Telematics system for identifying manufacturer-specific controller-area network data

ABSTRACT

Methods and systems for identifying manufacturer-specific controller-area (CAN) data for a vehicle type are provided. Manufacturer-specific CAN data may be identified by processing defined CAN data having a correlation relationship with the target data and undefined manufacturer-specific CAN data for determining if there is a correlation relationship therebetween. Also provided are methods and systems for identifying and automatically collecting manufacturer-specific CAN data for a vehicle type.

RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. § 119(e) to U.S.Provisional Application Ser. No. 63/068,923, filed on Aug. 21, 2020,which is herein incorporated by reference in its entirety.

BACKGROUND

Traffic data collection and analysis are routinely conducted by roadagencies, for example, government organizations responsible for trafficmanagement, road maintenance and/or road network planning. Road agenciesmay obtain measurements of traffic metrics, (e.g., traffic performance),from traffic data, to understand current traffic conditions at a roadwaysection of interest, such as a portion of a road or a traffic junction—alocation where multiple roads intersect, allowing traffic to change fromone road to another (e.g., intersection, roundabout, interchange).Traffic metrics are generally used to ascertain an existing, or topredict a future, need of changes to roadway infrastructure and/ortraffic control equipment. Examples of traffic metrics include trafficvolume, average vehicle speed, vehicle delay, among others.

Controller-area network messages transmitted between nodes on a vehicleCAN bus are often monitored by 3^(rd) party devices for diagnosticpurposes and for collection of vehicle operating data, for example, forfleet management. Although standardized CAN messages carrying specificvehicle operating data have been adopted by industry, most vehiclemanufacturers also employ non-standardized CAN messages forcommunication between nodes on a vehicle CAN bus. Suchmanufacturer-specific CAN messages may carry vehicle operating data thatwould be useful for fleet management.

Manufacturer-specific CAN messages carrying specific vehicle operatingdata vary not only between manufacturers, but often between differentvehicle models of the same make, and even between different years of thesame model. Furthermore, manufacturer-specific CAN messages carryingspecific vehicle operating data may even be different for a vehicle ofthe same make, model and year depending on when or where the vehicle wasmanufactured.

A common technique currently employed for reverse engineering ofmanufacturer-specific CAN messages requires a technician to gain accessto each vehicle to collect and analyze CAN data. Using such a method toidentify specific vehicle operating data carried inmanufacturer-specific CAN messages for each of the plethora of uniquevehicles is manually intensive, time consuming and prone to human error.

SUMMARY

According to a broad aspect there is a telematics system for identifyingmanufacturer-specific controller area network (CAN) data comprising: aplurality of monitoring devices, each thereof configured, for aplurality of first CAN IDs, for collecting CAN payload datacorresponding to the first CAN ID, collecting first reference datacorresponding to a second CAN ID having at least a first correlationrelationship with the manufacturer-specific CAN data, storing the firstreference data and the CAN payload data in a rolling buffer, followingreceipt of new first reference data and new CAN payload data,determining whether the first reference data present in the rollingbuffer meets a first criterion, in response to determining the firstreference data present in the rolling buffer meeting the firstcriterion, determining whether one or more first subsets of the CANpayload data present in the rolling buffer meets a second criterion,each of the one or more first subsets occupying a first byte position ineach slot of the rolling buffer, dependent on first reference datameeting the first criterion exceeding a first counting threshold, foreach of the one or more first subsets meeting the second criterionexceeding a second counting threshold, forming first position dataindicative of the first byte position in each slot of the rolling bufferoccupied thereby, forming first candidate data indicative of a firstcandidate of the manufacturer-specific CAN data corresponding to thefirst position data and the first CAN ID, a remote server in wirelesscommunication with each of the plurality of monitoring devices, theremote server configured for, selecting a subset of a plurality of thefirst candidate data corresponding to the first vehicle type to formsecond candidate data, selecting a second candidate from the secondcandidate data, and generating identification data corresponding to theidentity of the manufacturer-specific CAN data for the first vehicletype, the identification data indicative of a manufacturer-specific CANdata byte position and corresponding manufacturer-specific CAN data CANID associated with the second candidate data. The first reference datamay include first reference data corresponding to a second CAN ID andsecond reference data corresponding to a third CAN ID, the firstreference data and the second reference data having at least a firstcorrelation relationship with the manufacturer-specific CAN data.Collecting first reference data having at least a first correlationrelationship with the manufacturer-specific CAN data may includecollecting first reference data and second reference data having a firstcorrelation relationship with the manufacturer-specific CAN data.Selecting from the second candidate data a second candidate may includeselecting a second candidate indicated in the greatest number ofinstances of the second candidate data.

The telematics system for identifying manufacturer-specific controllerarea network (CAN) data wherein the first byte position may include aplurality of byte positions. The first criterion and the secondcriterion may be indicative of the at least first correlationrelationship. Determining whether the first reference data present inthe rolling buffer meets a first criterion may include determiningwhether the first reference data in each slot in the rolling bufferexceeds an immediately previously received first reference data by atleast a first predefined threshold. Determining whether the firstreference data present in the rolling buffer meets a first criterion mayinclude determining whether a value represented by the first referencedata in each slot in the rolling buffer exceeds a value represented byan immediately previously received first reference data by at least afirst predefined threshold. Determining one or more first subsets of theCAN payload data meets a second criterion may include determining foreach subset thereof, whether a difference between each consecutive pairof bytes in the first byte position of the rolling buffer exceeds asecond predefined threshold. Collecting first reference data having atleast a first correlation relationship with the manufacturer-specificCAN data may include collecting first reference data having a firstcorrelation relationship with the manufacturer-specific CAN data andcollecting first reference data having a second correlation relationshipwith the manufacturer-specific CAN data.

The plurality of monitoring devices may be further configured for, uponreceipt of the new first reference data and the new CAN payload data,determining whether the first reference data present in the rollingbuffer meets a third criterion in response to determining the firstreference data present in the rolling buffer meeting the thirdcriterion, determining whether one or more second subsets of the CANpayload data present in the rolling buffer meets a fourth criterion,each of the one or more second subsets occupying a second byte positionin each slot of the rolling buffer, dependent on the first referencedata meeting a third criterion exceeding a third counting threshold, foreach of the one or more second subsets meeting the fourth criterionexceeding a fourth counting threshold, forming second position dataindicative of the second byte position in each slot of the rollingbuffer occupied thereby, and wherein forming first candidate dataindicative of the first position data and the first CAN ID comprisesforming first candidate dependent on the first byte position of thefirst position data and the second byte position of the second positiondata being same, and the first CAN ID.

The telematics system for identifying manufacturer-specific controllerarea network (CAN) data wherein the third criterion and the fourthcriterion may be indicative of the second correlation relationship.Determining whether the first reference data in the rolling buffer meetsa third criterion may include determining whether a value represented bythe first reference data in each slot of the rolling buffer is within apredefined value of the average value represented thereby. Determiningwhether one or more second subsets of the CAN payload data present inthe rolling buffer meets a fourth criterion may include determiningwhether the relative difference in value of the one or more secondsubsets in each slot of the rolling buffer and the average value thereofdoes not exceed a predefined threshold. Collecting first reference datahaving a second correlation relationship with the manufacturer-specificCAN data may include collecting first reference data and secondreference data having a second correlation relationship with themanufacturer-specific CAN data.

The plurality of monitoring devices may be further configured forcollecting a plurality of second reference data corresponding to a thirdCAN ID having at least a second correlation relationship with the firstreference data and the manufacturer-specific CAN data, storing thesecond reference data in the rolling buffer, following receipt of thenew first reference data, new second reference data and the new CANpayload data, determining whether the first reference data present inthe rolling buffer meets a fifth criterion and the second reference datapresent in the rolling buffer meets a sixth criterion, in response todetermining the first reference data present in the rolling buffermeeting the fifth criterion and the second reference data present in therolling buffer meeting the sixth criterion, determining whether one ormore second subsets of the CAN payload data present in the rollingbuffer meets a fourth criterion, each of the one or more second subsetsoccupying a second byte position in each slot of the rolling buffer,dependent on the first reference data meeting a fifth criterion and thesecond reference data meeting the sixth criterion exceeding a thirdcounting threshold, for each of the one or more second subsets meetingthe fourth criterion exceeding a fourth counting threshold, formingsecond position data indicative of the second byte position in each slotof the rolling buffer occupied thereby, and wherein forming firstcandidate data indicative of the first position data and the first CANID comprises forming first candidate dependent on the first byteposition of the first position data and the second byte position of thesecond position data being same, and the first CAN ID. The fourthcriterion, fifth criterion and the sixth criterion may be indicative ofthe second correlation relationship. Determining whether the firstreference data present in the rolling buffer meets a fifth criterion mayinclude determining whether the value represented by first referencedata in each slot of the rolling buffer is within a predefined value ofthe average thereof. Determining whether the first reference datapresent in the rolling buffer meets a first criterion comprisesdetermining whether the first reference data and the second referencedata in the rolling buffer meets a first criterion.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are now described by way of non-limitingexample and are illustrated in the following figures in which likereference numbers indicate like features, and wherein:

FIG. 1 depicts a simplified diagram of a CAN 2.0A frame and a simplifieddiagram of an OBD2 message mapped to the CAN 2.0A frame;

FIG. 2 depicts simplified block diagrams of two exemplary OBD2 messages;

FIG. 3A depicts a simplified diagram of an exemplary fleet including aplurality of vehicles comprising various vehicle types;

FIG. 3B depicts simplified diagrams of exemplary manufacturer-specificCAN messages comprising odometer data each corresponding to one of fourvehicle types;

FIG. 4 depicts a simplified diagram of an exemplary telematics systemaccording to an embodiment;

FIG. 5 depicts a simplified block diagram of an exemplary monitoringdevice and a simplified block diagram of in-vehicle communication systemof a vehicle comprising CAN bus nodes according to an embodiment;

FIG. 6 depicts a simplified high-level flow diagram of a process foridentifying manufacture-specific CAN data, (i.e., target data), for avehicle type according to an embodiment;

FIG. 7A depicts a simplified flow diagram of a subprocess foridentifying one or more candidates for target data according to anembodiment;

FIG. 7B depicts a simplified flow diagram of another subprocess foridentifying one or more candidates for target data according to anembodiment;

FIG. 8A depicts a conceptual diagram of an exemplary rolling buffer;

FIG. 8B depicts a conceptual diagram of the contents of an exemplaryrolling buffer after collecting and storing a first sample of engineload data and CAN payload data;

FIG. 8C depicts a conceptual diagram of the contents of a rolling bufferafter collecting and storing four samples of engine load data andundefined payload data;

FIG. 8D depicts a conceptual diagram of contents of a rolling bufferafter collecting and storing seven samples of engine load data and CANpayload data;

FIG. 8E depicts a conceptual diagram of CAN payload data presentlystored in a rolling buffer;

FIG. 8F depicts a conceptual diagram of a subset of CAN payload datastored in a rolling buffer;

FIG. 9A depicts a table comprising exemplary engine load data presentlystored in a rolling buffer;

FIG. 9B depicts a table comprising exemplary CAN payload data bytespresently stored in a rolling buffer;

FIG. 9C depicts a table comprising exemplary CAN payload data bytes inposition [3,4] presently stored in a rolling buffer;

FIG. 9D depicts a table comprising exemplary CAN payload data bytes inposition [4,3] presently stored in a rolling buffer;

FIG. 10A depicts a conceptual diagram of exemplary first subset data;

FIG. 10B depicts an exemplary group of predefined subsets of CAN payloaddata that may be processed;

FIG. 10C depicts exemplary first position data based on first subsetdata;

FIG. 10D depicts exemplary first candidate data indicative of acandidate of the target data;

FIG. 11 depicts a simplified flow diagram of a subprocess foridentifying one or more candidates for target data according to anembodiment;

FIG. 12A depicts a table of exemplary engine load data presently storedin a rolling buffer;

FIG. 12B depicts a table comprising exemplary bytes presently stored ain rolling buffer;

FIG. 13A depicts a conceptual diagram of exemplary second subset data;

FIG. 13B depicts an exemplary group of predefined subsets CAN payloaddata that may be processed;

FIG. 13C depicts exemplary second position data;

FIG. 13D depicts exemplary first candidate data;

FIG. 14 depicts a simplified flow diagram of another subprocess foridentifying one or more candidates for target data according to anembodiment;

FIG. 15A depicts a conceptual diagram of the contents of a rollingbuffer;

FIG. 15B depicts a table comprising exemplary speed data presentlystored in a rolling buffer;

FIG. 16 depicts a simplified flow diagram of a subprocess foridentifying manufacturer-specific CAN data for a first vehicle typeaccording to an embodiment;

FIG. 17A depicts a conceptual diagram of exemplary first candidate datareceived by a remote server;

FIG. 17B depicts a table of exemplary vehicle type IDs;

FIG. 17C depicts exemplary second candidate data;

FIG. 17D depicts a conceptual diagram of exemplary data indicatingmanufacturer-specific CAN data;

FIG. 18 depicts a simplified flow diagram of a process for collectingmanufacture-specific CAN data according to an embodiment;

FIG. 19 depicts a simplified diagram of an exemplary telematics systemaccording to an embodiment;

FIG. 20A depicts another simplified diagram of an exemplary telematicssystem according to an embodiment;

FIG. 20B depicts yet another simplified diagram of an exemplarytelematics system according to an embodiment;

FIG. 21 depicts a simplified flow diagram of another subprocess foridentifying one or more candidates for target data based on a highcorrelation coefficient between a product of fourth reference data andfifth reference data, and CAN payload data, according to an embodiment;

FIG. 22A depicts a conceptual diagram of a rolling buffer of size 12;

FIG. 22B depicts a conceptual diagram of CAN payload data presentlystored in slots 1 to 12 of a rolling buffer;

FIG. 22C depicts a conceptual diagram of product data;

FIG. 22D depicts an exemplary subset of two bytes of CAN payload data inreverse ordered byte positions;

FIG. 23A depicts exemplary engine load values indicative of engine loaddata and exemplary RPM values indicative of RPM data presently stored ina rolling buffer;

FIG. 23B depicts exemplary values of product data;

FIG. 23C depicts exemplary values of first data;

FIG. 23D depicts exemplary values of a subset of CAN payload data;

FIG. 23E depicts exemplary values of second data;

FIG. 23F depicts exemplary values of third data;

FIG. 24A depicts first correlation coefficient data and correspondingfirst correlation coefficients between a subset CAN payload data andproduct data;

FIG. 24B depicts a conceptual diagram of first candidate data;

FIG. 25 depicts a simplified flow diagram of another subprocess foridentifying one or more candidates for target data based on a highcorrelation coefficient between a product of fourth reference data andfifth reference data, and CAN payload data, according to an embodiment;

FIG. 26A depicts first correlation coefficient data and exemplary valuesthereof;

FIG. 26B depicts first correlation coefficient data and exemplary valuesthereof;

FIG. 26C depicts first correlation coefficient data and exemplary valuesthereof;

FIG. 26D depicts first correlation coefficient data and exemplary valuesthereof;

FIG. 26E depicts first correlation coefficient data and exemplary valuesthereof;

FIG. 26F depicts averaged first correlation coefficient data andexemplary values thereof;

FIG. 27 depicts a simplified flow diagram of another subprocess foridentifying one or more candidates for target data based on a highcorrelation coefficient between a product of fourth reference data andfifth reference data, and CAN payload data, according to an embodiment;

FIG. 28A depicts exemplary values of fourth data;

FIG. 28B depicts exemplary values of fifth data;

FIG. 28C depicts second correlation coefficient data and correspondingsecond correlation coefficients between a subset CAN payload data andproduct data;

FIG. 28D depicts a conceptual diagram of first candidate data;

FIG. 29 depicts a simplified flow diagram of another subprocess foridentifying one or more candidates for target data based on a highcorrelation coefficient between a product of fourth reference data andfifth reference data, and CAN payload data, according to an embodiment;

FIG. 30A depicts second correlation coefficient data and exemplaryvalues thereof;

FIG. 30B depicts second correlation coefficient data and exemplaryvalues thereof;

FIG. 30C depicts second correlation coefficient data and exemplaryvalues thereof;

FIG. 30D depicts second correlation coefficient data and exemplaryvalues thereof;

FIG. 30E depicts second correlation coefficient data and exemplaryvalues thereof;

FIG. 30F depicts averaged second correlation coefficient data andexemplary values thereof;

FIG. 31A depicts a conceptual diagram of data, including CAN payloaddata, fourth reference data, and fifth reference data received by amonitoring device at predefined intervals;

FIG. 31B depicts a conceptual diagram of a rolling buffer;

DESCRIPTION

An engine control unit (ECU) is an embedded computer for controllingmechanical and/or electrical vehicle systems/subsystems. For instance,an ECU may receive an input from a sensor or other ECU and use actuatorsto control functionalities of the vehicle. An example of an ECU is anengine control module (ECM) that controls a series of actuators on aninternal combustion engine to ensure optimal engine performance. It doesthis by reading values from a multitude of sensors within the enginebay, interpreting the data, and adjusting the engine actuators.

ECUs may receive inputs from sensors and switches that sense/measurevehicle variables such as temperature, pressure, voltage, acceleration,braking of the vehicle, steering angle, engine revolutions per minute(RPM), among others.

Although some ECUs form independent subsystems, communication betweenother ECUs is necessary for proper vehicle operation. In some instances,ECUs communicate vehicle information relating to a sensed/measuredvehicle variable to other ECUs. For example, the Anti-Lock Brake System(ABS) may receive information from the Powertrain Control Module (PCM)to determine whether the traction control is working.

Communication between vehicle components is facilitated by one or morecontroller-area networks (CAN(s)). ECUs, and other vehicle components,may communicate by transmitting standardized CAN frames over a CAN bus.For example, CAN 2.0A and CAN 2.0B standards for in-vehiclecommunication systems are well known in the art.

Illustrated in FIG. 1 is a simplified diagram of a typical CAN 2.0Aframe 100 comprising, a start of frame bit (SOF) 102, 11-bit CANidentifier (ID) 104, remote transmission request bit (RTR) 106, 2-bitreserved field 107, 4-bit data length code (DLC) 108 indicating thenumber of data bytes in the payload data, 8-byte CAN payload data 110,16-bit cyclical redundancy check (CRC) 112, 2-bit acknowledgement field114, and a 7-bit frame delimiter indicating end of frame (EOF) 116. Inaddition to fields of a CAN 2.0A frame, a CAN 2.0B frame includes an18-bit identifier extension allowing for additional nodes on the CAN busand for the transport of messages that exceed the 8-byte maximum of CAN2.0A frames. 8-byte CAN payload data 110 may include any number of 0 upto 8 bytes.

An ECU may continuously broadcast CAN frames on a CAN bus. In someinstances, an ECU may transmit sensor, programming information and/orvehicle variable information at frequent and regular intervals,regardless if the information has been requested or not. For example, anECU may transmit a CAN message every, 50 ms, 100 ms, 500 ms, or atanother time interval. On a CAN bus there is no central hub or routingsystem, just a continuous flow of broadcasted CAN messages. Each ECUmonitors the CAN bus to detect relevant data from the plethora of CANmessages for it to carry out its work.

In some instances, higher-layer communication protocols forcommunicating over a vehicle bus (e.g., CAN bus) have been adopted byindustry. These protocols are documented in vehicle bus standards whichspecify a set of defined CAN messages embedded in CAN frames. Suchstandards may provide a definition of a CAN message, including CAN ID,meaning/format of the corresponding CAN payload data, and dataconversion rules, if applicable.

For example, the Society of Automotive Engineers (SAE) standard J1939 isa vehicle bus standard commonly used for communication and diagnosticsamong vehicle components, e.g., ECUs, of commercial vehicles, e.g.,heavy duty vehicle. This standard describes a common messaging protocolfor transferring vehicle variable values and control information betweennodes on a CAN bus. SAE 1939 further defines standard message formatsfor vehicle diagnostic data as well as a J1939 connector enabling accessto an in-vehicle communication bus. For example, a 3rd party device maybe coupled to a CAN bus via a J1939 connector for collecting vehiclediagnostic information, communicating with vehicle components andmonitoring vehicle information exchanged between nodes on the CAN bus.

In another example, the SAE J1962 standard is a vehicle bus standardcommonly used for diagnostics among consumer vehicles, e.g., cars, lightduty trucks. This standard describes a common messaging protocol forcommunicating with a vehicle's self-diagnostic system (i.e., on-boarddiagnostics II (OBD2)) as well as an OBD2 connector enabling access to aCAN bus. For example, a 3rd party device may couple to a CAN bus via anOBD2 connector for collecting vehicle diagnostic information,communicating with vehicle components and monitoring vehicle informationexchanged between nodes on the CAN bus.

Referring again to FIG. 1 , illustrated is a simplified diagram of anOBD2 message 120 defined in SAE J1962 standard mapped to CAN 2.0A frame100. In this example, message 120 comprises an 11-bit identifier (ID)122 corresponding to CAN ID 104. The remaining portion of OBD2 message120 corresponds to CAN payload data 110 and comprises 1-byte lengthfield 124, 1-byte mode field 126, 1-byte parameter ID field 128, 1-bytedata fields including: Ah 130, Bh 132, Ch 134, Dh 136, and a 1-byteunused field 138. SAE J1962 standard describes in detail how to createand decode OBD2 messages, including ID, the meaning/format of messagefields and data conversion rules for interpreting data.

For example, shown in FIG. 2 are simplified block diagrams of twoexemplary OBD2 messages, message 200, 220, each defined in the SAE J1962standard. Message 200 comprises ID 202, 7DFh, indicating that message200 is a request message. Length field 204, 0x02, indicates that thenext two bytes, mode field 206 and PID field 208, comprise valid data.Remaining bytes, Ah-Dh fields and unused field, 210-215, respectively,are to be ignored. A length field of an OBD2 message may have a value of0x02 to 0x07. Mode field 206, 0x01, indicates that the request is forcurrent data. For request messages, a mode field may have a value in therange 0x01 to 0Ah. In message 200, PID field 208 is 0D. For mode 01, aPID 0D indicates vehicle speed. Accordingly, message 200 may beunderstood as a request for a vehicle's current speed.

Message 220 comprises ID 222, 0x7E8, indicating that message 220 is aresponse message, possibly a response to message 200. In responsemessages, an ID also identifies the CAN node that is transmitting aresponse and may have a value of 0x7E8 to 0x7EF. Length field 224, 0x03,indicates that the next three bytes, mode field 226, PID field 228, andAh field 230, comprise valid data. The remaining bytes, Bh-Dh fields andunused field, 232-235, respectively, are to be ignored. Mode field 226,0x41, indicates that message 220 comprises current data. For responsemessages, the mode field may have a value in the range of 0x41 to 4Ah.In message 220, PID field 228 is 0D. For mode 41, a PID of 0D, specifiesdata bytes in the OBD2 message indicate speed and a data conversionrule. In this example, the data conversion rule for determining thevehicle speed from data byte Ah field 230, 0x32, is to convert thehexadecimal (Hex) value thereof in into decimal (Dec), i.e., 0x32indicates a speed of 50 km/h.

As mentioned hereinabove, vehicle bus standards, e.g., J1939, J1962,have been adopted by industry. Accordingly, CAN message definitionsspecified in vehicle bus standards are implemented across vehiclemanufacturers. Thus, vehicles having in-vehicle communication systemssupporting a same vehicle bus standard, exchange data, e.g., speed data,in a same CAN message format.

Although CAN messages for transmitting some vehicle data are defined byvehicle bus standards, CAN messages for transmitting all possiblevehicle data are defined in vehicle bus standards. In suchcircumstances, a vehicle manufacturer may define a unique CAN messagefor communicating vehicle data on a vehicle's CAN bus.

For example, a vehicle manufacturer may select an available CAN ID,(e.g., a CAN ID unreserved in one or more vehicle bus standards) anddesignate bytes of the corresponding CAN payload data to representspecific data. Optionally, a vehicle manufacturer may also create dataconversion rules, if necessary. Such manufacturer defined CAN messagesare referred to herein as manufacturer-specific CAN messages.

For instance, an ECU may collect specific vehicle information that is tobe shared with other ECUs on a CAN bus. However, a CAN messagecomprising data indicative of this specific vehicle information has notbeen specified in any vehicle bus standard supported by the vehicle. Assuch, the vehicle manufacturer may define a CAN message forcommunicating the specific vehicle information between nodes (e.g.,ECUs) on the CAN bus.

In practise, manufacturer-specific CAN messages are often unique to avehicle type. Vehicle types may be defined by vehicle make, vehicle makeand model, and/or vehicle make, model and year.

For instance, exemplary vehicle types defined by vehicle make include,Ford, Buick, Mercedes-Benz, Toyota, and the like. Examples of a vehicletype defined by vehicle make and model include Ford F-150, Buick Encore,Mercedes-Benz Metris Van, Toyota Corolla, and the like. Finally,examples of a vehicle type defined by vehicle make, model and yearinclude, 2017 Ford F-150, 2016 Buick Encore, 2006 Mercedes-Benz MetrisVan, 2014 Toyota Corolla, and the like.

Shown in FIG. 3A is a simplified diagram of an exemplary fleet 300including a plurality of vehicles comprising various vehicle types. Forexample, fleet 300 comprises vehicles 302, 304, 306 and 308corresponding to vehicle types, 2017 Ford F-150, 2016 Buick Encore, 2006Mercedes-Benz Metris Van and 2014 Toyota Corolla, respectively.

In this example, there is no standard CAN message comprising odometerdata defined in any vehicle bus standard supported by the vehicles infleet 300. As such, each vehicle manufacturer creates amanufacturer-specific CAN message, unique to each vehicle type, forcommunicating odometer data on a CAN bus. For example, shown in FIG. 3B,are exemplary manufacturer-specific CAN messages 312 a, 312 b, 312 c and312 d comprising odometer data corresponding to each of the four vehicletypes, 2017 Ford F-150, 2016 Buick Encore, 2006 Mercedes-Benz Metris Vanand 2014 Toyota Corolla, respectively.

For example, vehicle manufacturer of vehicle 302 definesmanufacturer-specific CAN message 312 a for communicating odometer dataover a CAN bus for vehicle type 2017 Ford F-150. Manufacturer-specificCAN message 312 a is assigned CAN ID 313 a, 0x031, and bytes inpositions 0 to 2 of the corresponding CAN payload data 314 a arespecified as comprising odometer data. Data in payload bytes 3 to 7 areinvalid and are to be ignored. In this instance, odometer data carriedin payload bytes 0 to 2 of CAN payload data 314 a is 0x01396A. A dataconversion rule to calculate the odometer value is to convert the hexnumber into decimal, i.e., 0x01396A=80234 km.

In a second example, vehicle manufacturer of vehicle 304 definesmanufacturer-specific CAN message 312 b for communicating odometerinformation over a CAN bus for vehicle type 2016 Buick Encore.Manufacturer-specific CAN message 312 b is assigned CAN ID 313 b, 0x0A7,and bytes in positions 2 to 4 of the corresponding CAN payload data 314b are specified as comprising odometer data. Data in payload bytes 0, 1,and 5 to 7 are invalid and are to be ignored. In this instance, odometerdata carried in payload bytes 2 to 4 of CAN payload data 314 b is0x044440. A data conversion rule to calculate the odometer value is toconvert the hex number into decimal, i.e., 0x044440=279616 km.

In a third example, vehicle manufacturer of vehicle 306 definesmanufacturer-specific CAN message 312 c for communicating odometerinformation over a CAN bus for vehicle type 2006 Mercedes-Benz MetrisVan. Manufacturer-specific CAN message 312 c is assigned CAN ID 313 c,0x0DA, and bytes in positions 5 to 7 of the corresponding CAN payloaddata 314 c are specified as comprising odometer data. Data in payloadbytes 0 to 4 are invalid and are to be ignored. In this instance,odometer data carried in payload bytes 5 to 7 of CAN payload data 314 cis 0x098C93. A data conversion rule to calculate the odometer value isto convert the hex number into decimal, i.e., 0x098C93=625811 km.

In a fourth example, vehicle manufacturer of vehicle 308 definesmanufacturer-specific CAN message 312 d for communicating odometerinformation over a CAN bus for vehicle type 2014 Toyota Corolla.Manufacturer-specific CAN message 312 d is assigned CAN ID 313 d, 0x0EE,and bytes in positions 1 to 3 of the corresponding CAN payload data 314d are specified as comprising odometer data. Data in payload bytes 0,and 4 to 7 are invalid and are to be ignored. In this instance, odometerdata carried in payload bytes 1 to 3 of CAN payload data 314 d is0x01223C. A data conversion rule to calculate the odometer value is toconvert the hex number into decimal, i.e., 0x01223C=74300 km.

As described hereinabove, manufacturer-specific CAN messages carrying asame vehicle information, e.g., odometer data, may have a unique foreach vehicle type. In contrast, defined CAN messages provided inindustry adopted standards may be supported by all vehicle types.

However, defined CAN data may include any CAN data having a knowndefinition, e.g., known data type, data byte position(s) andcorresponding CAN ID. Specific and non-limiting examples of defined CANdata may include data defined in an industry bus standard, andmanufacturer-specific CAN data wherein a definition thereof has beendetermined.

A fleet comprising four vehicle types is described in this example forexplanation purposes only and embodiments are not intended to be limitedto the examples described herein. In practise, a fleet may comprise oneor more vehicle types.

Telematics System

Now referring to FIG. 4 , shown is a simplified diagram of an exemplarytelematics system according to an embodiment. Telematics system 400comprises a remote server 404 having a network interface 412 and aplurality of monitoring devices 402 a, 402 b, and 402 c, each thereofhaving network interfaces, 410, 412, respectively. Remote server furtherincluding a processing resource, datastore, RAM or another type ofmemory device. The datastore may be or include one or morenon-transitory computer-readable storage media, such as optical,magnetic, organic, or flash memory, among other data storage devices andmay take any form of computer readable storage media.

Remote server 404 and monitoring devices 402 are configured for couplingto a communication network, for example, communication network 406, asshown in FIG. 4 . Communication network 406 may include one or morecomputing systems and may be any suitable combination of networks orportions thereof to facilitate communication between network components.Communication network 406 may operate according to one or morecommunication protocols, such as, Universal Mobile TelecommunicationsService (UMTS), GSM, Enhanced Data Rates for GSM Evolution (EDGE), LTE,CDMA, LPWAN, Wi-Fi, Bluetooth, Ethernet, HTTP/S, TCP, and CoAP/DTLS, orother suitable protocol. Communication network 406 may take other formsas well.

Monitoring device 402 also includes a CAN bus interface 414 forcommunicatively coupling to a CAN bus of corresponding vehicle 408, asshown in FIG. 4 .

Alternatively, telematics system 400 may comprise up to ‘n’ monitoringdevices, as indicated by monitoring device 402 n, in FIG. 4 . Examplesof monitoring devices described above are provided for explanationpurposes only and embodiments are not intended to be limited to theexamples described herein.

Shown in FIG. 5 is a simplified block diagram of exemplary monitoringdevice 402 comprising processing resource 504, datastore 506, e.g., RAMor another type of memory device, a CAN communication device 502providing CAN bus interface 412, and a network communication device 508,e.g., wireless modem, providing network interface 410 to a communicationnetwork, such as communication network 406.

In this example, monitoring device 402 is communicatively coupled to CANbus 512 of vehicle 408, via CAN bus interface 412, as shown.Communication device 502 may support wired communication to a CAN bus,for instance, via an OBD2 connector. Alternatively, communication device502 may support wireless communication to a CAN bus, for example, viaBluetooth®, Wi-Fi, or other wireless communication technology.

Also illustrated in FIG. 5 is a simplified block diagram of in-vehiclecommunication system 514 of vehicle 408 comprising CAN bus nodes 510,e.g., ECUs, communicatively coupled to CAN bus 512. In this example,monitoring device 402 monitors information exchanged between nodes onCAN bus 512 and collects data that may be useful for fleet managementand monitoring. Monitoring device 402 then transmits this data to remoteserver 404 for future use.

In a first instance, in-vehicle communication system 514 of vehicle 408supports the SAE J1962 standard. Monitoring device 402 may be configuredto detect and log specific data carried in a CAN message defined in theSAE J1962 standard.

For example, SAE J1962 standard provides a definition of a CAN messagecomprising speed data specified to have a CAN ID 0x78E and speed datacarried in byte 3 of the CAN payload data. Shown in FIG. 2 is anexemplary CAN message, message 220, defined in SAE J1962 standardcomprising speed data. In this example, monitoring device 402 may beconfigured to identify CAN messages having CAN ID 0x78E and to savespeed data, 0x32, stored in byte 3 228. Speed data 0x32 may be stored,for example, in datastore 506 of monitoring device 402. Monitoringdevice 402 transmits speed data 0x32 to remote server 404 for futureprocessing.

Monitoring device 402 may collect speed data from any vehicle, and/orvehicle type, provided the vehicle's in-vehicle communication systemsupports SAE J1962 standard. For example, monitoring device 402 maycollect speed data from the following exemplary vehicle types, 2017 FordF-150, 2016 Buick Encore, 2006 Mercedes-Benz Metris Van, and others, byidentifying CAN messages with CAN ID 0x78E and storing data in byte 3 ofthe corresponding CAN payload data.

Similarly, monitoring device 402 may collect any data carried in a CANmessage from any vehicle, and/or vehicle type, provided the vehicle'sin-vehicle communication system supports SAE J1962 standard. Forinstance, a same data, e.g., RPM, engine load . . . , may be collectedby monitoring device 402 from a plurality of vehicle types based on adefinition of the CAN message carrying that data specified in SAE J1962standard.

In some instances, manufacturer-specific CAN messages may also comprisedata useful for fleet management and monitoring. However, as definitionsof manufacturer-specific CAN messages may be unknown (e.g., not publiclyavailable) such data may be undetectable by a 3rd party. For example,monitoring device 402 cannot be configured to collect data unless theCAN ID and meaning/format of CAN payload data of a CAN message carryingthat data of is known.

Furthermore, for a monitoring device 402 to collect a same data from aplurality of vehicle types, the definition of a CAN message carryingthat same data for each vehicle type must also be known.

For instance, a CAN message carrying odometer data is not specified in avehicle bus standard supported by any vehicles in fleet 300 in FIG. 3A.In order for a monitoring device 402 to collect odometer data for eachvehicle therein, a definition of a manufacturer-specific CAN messages312 a-312 d carrying odometer data for each vehicle type in fleet 300must be known.

For example, for vehicle 302—vehicle type 2017 Ford F-150, monitoringdevice 402 is be configured to collect CAN payload data bytes 0 to 2corresponding to CAN ID 0x031. For vehicles 304—vehicle type 2016 BuickEncore, monitoring device 402 is be configured to collect CAN payloaddata bytes 0 to 2 corresponding to CAN ID 0x0A7. For vehicles306—vehicle type 2006 Mercedes-Benz Metris Vans, monitoring device 402is be configured to collect CAN payload data bytes 5 to 7 correspondingto CAN ID 0x0DA. For vehicles 308—vehicle type 2014 Toyota Corollas,monitoring device 402 is be configured to collect CAN payload data bytes1 to 3 corresponding to CAN ID 0x0EE.

In some instances, vehicle variables may be correlated one to another.For example, vehicle variables fuel consumption (i.e., rate of fuelconsumption) and engine load are correlated. An exemplary correlationrelationship between fuel consumption and engine load may becharacterized as an increase in engine load correlates to an increase infuel consumption. Subsequently, it is reasonable to expect data (e.g.,data transmitted by ECUs that sense/measure vehicle variables),representing correlated vehicle variables have a similar correlationrelationship.

For example, if engine load and fuel consumption are correlated, it isanticipated that engine load data and fuel rate data have a similarcorrelation relationship. For instance, fuel rate data indicates therate of fuel consumption of the vehicle at the time of collectionthereof. One of ordinary skill in the art will appreciate that acorrelation relationship between vehicle variables may be specifiedbased on, for example, an understanding of vehicle operation, empiricaltesting, and/or by another means.

Described herein are various embodiments relating to identifyingmanufacturer-specific CAN data, also referred to herein as target data.Some embodiments relate to utilizing a known correlation relationshipbetween target data, representing a first vehicle variable, and firstreference data, representing a second vehicle variable, for identifyingtarget data. Identifying target data may include processing CAN payloaddata of undefined CAN messages, (e.g., CAN messages not defined in avehicle bus standard), and first reference data for determining whetherCAN payload data, and/or a portion thereof, satisfies the knowncorrelation relationship therebetween.

Various embodiments relate to utilizing one or more known correlationrelationships between target data representing a first vehicle variableand one or more reference data representing other vehicle variables foridentifying target data.

Identifying target data may include identifying a CAN ID of a CANmessage carrying target data and byte position(s) of target data withincorresponding CAN payload data.

Process 600

Shown in FIG. 6 is a simplified high-level flow diagram of a process 600for identifying manufacture-specific CAN data, i.e., target data, for avehicle type according to an embodiment. Process 600 comprises one ormore subprocesses 601 and subprocess 602, as shown.

Subprocess 601 may include utilizing at least one correlationrelationship between target data and at least one reference data foridentifying one or more candidates for target data. The one or morecandidates are associated with a vehicle type. Subprocess 601 providesfirst candidate data indicative of the one more candidates, tosubprocess 602.

A plurality of subprocesses 601 may provide a plurality of firstcandidate data associated with a plurality of vehicle types.

Subprocess 602 may include processing first candidate data provided bysubprocess(es) 601 for identifying target data specific to a vehicletype. Identifying target data specific to a vehicle type may includeidentifying a CAN ID and byte position(s) of target data withincorresponding CAN payload data.

For purposes of illustration, process 600 is described as being carriedout by telematics system 400. In particular, subprocess 601 is describedas being carried out by monitoring device 402 and subprocess 602 isdescribed as being carried out by remote server 404. However, process600, subprocess 601 and subprocess 602 may be carried out by acombination of other systems, subsystems, devices or other suitablemeans provided the operations described herein are performed. Process600 may be automated, semi-automated and some blocks thereof may bemanually performed.

Subprocess 700

Illustrated in FIG. 7A is a simplified flow diagram of a subprocess 700for identifying one or more candidates for target data according to anembodiment. Subprocess 700 may include identifying candidates based on afirst correlation relationship between a target data and a firstreference data.

For instance, a target data may be in the form of fuel rate data and afirst reference data may be in the form of engine load data. Anexemplary first correlation relationship between fuel consumption andengine load may be characterized as an increase in engine loadcorrelates to an increase in fuel consumption.

Starting at block 701A, subprocess 700 may include selecting a first CANID from a group of available CAN IDs. Some examples of available CAN IDsmay include unreserved CAN IDs in the SAE J1939 standard, the SAE J1962standard, and/or other vehicle bus standards.

In the present example, monitoring device 402 selects first CAN ID 0x400from a group of available CAN IDs comprising 0x001 to 0x7FF. However,any available CAN ID from the group may be selected.

At block 701B, subprocess 700 may include collecting a plurality offirst reference data and a plurality of CAN payload data from a CAN busand storing that data in a rolling buffer of size S.

In some instances, first reference data and CAN payload data arecollected at predefined intervals. Once all S slots of the rollingbuffer are filled, subprocess 700 proceeds to the next block.Notwithstanding subprocess 700 proceeding to block 702, samples of firstreference data and CAN payload data may continue to be collected andstored in the rolling buffer at predefined intervals.

Shown in FIG. 8A is a conceptual diagram of an exemplary rolling buffer800 of size 7. In the present example, monitoring device 402 collectsfirst reference data in the form of engine load data 804 and CAN payloaddata corresponding to first CAN ID 0x400 from a CAN bus, such as, CANbus 512, at a predefined interval of 1 s. Engine load data and CANpayload data is then stored in rolling buffer 800. In this example,rolling buffer is size 7, however, a rolling buffer may have any numberof slots.

For descriptive purposes, first reference data and CAN payload data aredescribed to be collected at a predefined interval of 1 second. Inpractise, however, first reference data and CAN payload data may becollected at another predefined interval.

Alternatively, each of the plurality of CAN payload data is collected ata time temporally proximate a time each of the plurality of firstreference data is collected. For example, CAN payload data may becollected at the same time as, or at a time close to, the time firstreference data is collected.

Now referring to FIG. 8B, shown is a conceptual diagram of the contentsof rolling buffer 800 after collecting and storing a first sample ofengine load data 804 and CAN payload data 807. For example, firstreference data 804 a and CAN payload data 807 a are stored in slot 1 ofrolling buffer 800, whereas slots 2 to 7 comprise invalid data and/or nodata.

In FIG. 8C, shown is a conceptual diagram of the contents of rollingbuffer 800 after collecting and storing four samples of engine load data804 and undefined payload data 807. For example, rolling buffer 800comprises first reference data 804 d to 804 a in slots 1 to 4,respectively, and CAN payload data 807 d to 807 a in slots 1 to 4,respectively. Slots 5 to 7 of rolling buffer 800 comprise invalid dataand/or no data.

Finally, in FIG. 8D, shown is a conceptual diagram of the contents ofrolling buffer 800 after collecting and storing seven samples of engineload data 804 and CAN payload data 807. For example, rolling buffer 800comprises first reference data 804 g to 804 a in slots 1 to 7,respectively, and CAN payload data 807 g to 807 a in slots 1 to 7,respectively. Once each slot of rolling buffer 800 is filled, subprocess700 may proceed to the next block.

Although subprocess 700 proceeds to block 702, samples of firstreference data 804 and CAN payload data 807 continue to be collected andstored in rolling buffer 800 by monitoring device 402 at predefinedintervals of 1 second.

Next, at block 702, subprocess 700 includes monitoring the rollingbuffer and, upon receipt of new first reference data and new CAN payloaddata, subprocess 700 proceeds to the next block.

For example, monitoring device 402 monitors rolling buffer 800 and uponstorage of new engine load data 804 g and CAN payload data 807 g, forexample in slot 1, subprocess 700 proceeds to the next block.

At block 704, subprocess 700 may include determining whether the firstreference data stored in the rolling buffer provides a valid testcondition for evaluating whether the first reference data and CANpayload data satisfy the first correlation relationship.

A specific and non-limiting example of a method for determining whetherthe first reference data provides a valid test condition is bydetermining whether the first reference data meets a first criterionindicative of the first correlation relationship. An exemplary firstcriterion may be engine load represented by engine load data 804 inrolling buffer 800 exceeds the engine load represented by an immediatelypreviously received engine load data 804 by a first predefinedthreshold, for instance, 49%.

Referring now to FIG. 9A, shown is table 901 comprising exemplary engineload data 804 a-804 g presently stored in rolling buffer 800. Table 901includes the value of engine load data 804 a-804 g in Hex 902 and in Dec903, and engine load 904 calculated as per data conversion rule, engineload=(Dec*100/255). Engine load 904 is a percentage of load on an engineand may range between [0-100%]. In addition, table 901 includes therelative percentage load increase 905 between an engine load 904 inrolling buffer 800 and an immediately previously received engine load904.

In the present example, monitoring device 402 calculates the actualengine load 904 using the data conversion rule described hereinabove.Next, monitoring device 402 determines the relative percentage loadincrease 905 between each engine load 904 indicated by engine load data804 and an engine load 904 indicated by an immediately previouslyreceived engine load data 804.

For example, engine load data 804 g in slot 1 indicates an engine loadof 3.9%. The immediately previously received engine load data 804 ofengine load data 804 g is engine load data 804 f in slot 2. Engine loaddata 804 f indicates an engine load of 5.9%. The relative percentageload increase therebetween is 51%, (i.e., (5.9−3.9)/3.9=51%).

Monitoring device 402 determines the relative percentage load increase905 between the remaining engine load 904 indicated by engine load data804 f-804 b and an engine load 904 indicated by an immediatelypreviously received engine load data 804 e-804 a, respectively, as shownin FIG. 9A. As each of the relative percentage load increase 905 exceedsthe first predefined threshold, 49%, engine load data 804 meets thefirst criterion.

Still at block 704, subprocess 700 may include incrementing a firstcounter provided the first reference data meets the first criterion. Thefirst counter indicates the total number of instances first referencedata provides a valid test condition for evaluating whether the firstreference data and CAN payload data satisfy the first correlationrelationship. If the first reference data provides a valid testcondition for evaluating whether the first reference data and CANpayload data satisfy the first correlation relationship subprocess 700proceeds to block 706, otherwise, subprocess 700 proceeds to block 702.

In the present example, engine load data 804 met the first criterionindicating engine load data 804 provided a valid test condition forevaluating whether the engine load data 804 and CAN payload data satisfythe first correlation relationship. Thus, monitoring device 402increments a first counter by 1 and subprocess 700 proceeds to block706.

The first criterion described in this example is provided forexplanation purposes only and embodiments are not intended to be limitedto the examples described herein.

Next, at block 706, subprocess 700 may include processing CAN payloaddata for identifying one or more subsets of the CAN payload datasatisfying the first correlation relationship. If one or more of thesubsets satisfies the first correlation relationship, subprocess 700proceeds to block 707, otherwise subprocess returns to block 702.

Shown in FIG. 8E, is a conceptual diagram of CAN payload data 807 g to807 a presently stored in slots 1 to 7, respectively, of rolling buffer800. For instance, CAN payload data 807 g in slot 1 includes byte 807 gain byte position [0], 807 gb in byte position [1], 807 gc in byteposition [2], 807 gd in byte position [3], 807 ge in byte position [4],807 gf in byte position [5], 807 gg in byte position [6], and 807 gh inbyte position [7], as indicated in FIG. 8E. Similarly, CAN payload data807 f in slot 2 comprises bytes 807 fa to 807 fh corresponding to bytepositions [0] to [7], respectively, and so forth.

Target data may be comprised of one or more bytes in any byte positions[0] to [7] of an undefined CAN message payload. Accordingly, processingCAN payload data for determining one or more subsets of the CAN payloaddata that satisfies the first correlation relationship may includeprocessing a plurality of subsets of data of CAN payload data in anybyte position(s) [0] to [7].

A specific and non-limiting example of a method for determining whetherone or more subsets of CAN payload data satisfies the first correlationrelationship may include determining whether the one or more subsets ofthe CAN payload data meets a second criterion indicative of the firstcorrelation relationship. An exemplary second criterion may be arelative increase between consecutive pairs of data in a same byteposition in the rolling buffer exceeds a second predefined threshold,for instance, 20%.

In a first instance, determining whether a subset of CAN payload datasatisfies the first correlation relationship may include processingsingle bytes in a same byte position of CAN payload data in each slot ofthe rolling buffer.

For example, monitoring device 402 processes subset 811, shown in FIG.8E, for determining whether subset 811 meets the second criterion.Subset 811 includes single bytes of CAN payload data 807 occupying asame byte position, position [0]. For instance, monitoring device 402processes subset 811 for determining the relative increase between thefollowing consecutive pairs of single bytes in position [0] in rollingbuffer 800: (807 ga and 807 fa) (807 fa and 807 ea), (807 ea and 807da), (807 da and 807 ca), (byte 807 ca and byte 807 ba), and (807 ba and807 aa). Next, monitoring device 402 then determines whether therelative increase between the consecutive pairs of single bytes exceedsthe second predefined threshold, 20%.

Shown in FIG. 9B is table 906 comprising exemplary bytes 804 ga-804 aapresently stored in rolling buffer 800. Table 906 includes exemplaryvalues of bytes 804 ga-804 aa in Hex 907 and Dec 908. Also included intable 906 is an example of the relative increase 910 between consecutivepairs of bytes in position [0] in the rolling buffer 800 determined bymonitoring device 402.

In this example, the relative increase of each consecutive pair of bytessubset exceeds the second predefined threshold 20% indicating thatsubset 811 meets the second criterion. As such, subset 811 correspondingto CAN ID 0x400, byte position [0], may be a candidate for target data.

In the present example, since subset 811 meets the second criterion,subprocess 700 proceeds to block 707. However, if subset 811 did notmeet the second criterion subprocess would proceed to block 708.

Additionally, and/or alternatively, one or more subsets comprised ofsingle bytes in another byte position of CAN payload data, position [1]to [7], may be processed.

In another instance, determining whether a subset of CAN payload datasatisfies the first correlation relationship may include processing aplurality of ordered bytes in same byte positions of the CAN payloaddata in each slot of the rolling buffer. The same byte positions mayinclude any byte positions [0] to [7]. Some examples of a plurality ofordered bytes that may be processed include bytes in the following bytepositions: [0,1], [1,2], [2,3], [3,4], [4,5], [5,6], [6,7], [0,1,2],[1,2,3], [2,3,4], [3,4,5], [4,5,6], [5,6,7], among others.

For example, monitoring device 402 processes subset 812, shown in FIG.8E, for determining whether subset 812 meets the second criterion.Subset 812 includes two ordered bytes of CAN payload data in a same byteposition, position [3,4].

For instance, monitoring device 402 processes subset 811 for determiningthe relative increase between the following consecutive pairs of twoordered bytes in positions [3,4] in rolling buffer 800: ([807 gd, 807ge] and [807 fd, 807 fe]), ([807 fd, 807 fe] and [807 ed, 807 ee]),([807 ed, 807 ee] and [807 dd, 807 de]), ([807 dd, 807 de] and [807 cd,807 ce]), ([807 cd, 807 ce] and [807 bd, 807 be]), and ([807 bd, 807 be]and [807 ad, 807 ae]). Next, monitoring device 402 then determineswhether the relative increase between the consecutive pairs of twoordered bytes exceeds the second predefined threshold, 20%.

Shown in FIG. 9C is table 907 comprising exemplary bytes in position[3,4] presently stored in rolling buffer 800. Table 906 includes thevalue of bytes [807 gd, 807 ge] to [807 ad, 807 ae]in Hex 9011 and Dec912. Also included in table 906 is an example of the relative increase913 between the consecutive pairs of ordered bytes in position [3,4] inthe rolling buffer 800 determined by monitoring device 402. In thisexample, the relative increase between each consecutive pair of orderedbytes in position [3,4] exceeds the second predefined threshold 20%indicating that subset 812 meets the second criterion. As such, subset812 corresponding to CAN ID 0x400, byte positions [3,4], may be acandidate for target data.

In the present example, since subset 812 meets the second criterion,subprocess 700 proceeds to block 707. However, if subset 812 did notmeet the second criterion subprocess 700 would proceed to block 708.

Additionally, and/or alternatively, one or more subsets comprised of twoordered bytes in other byte positions of CAN payload data, other thanpositions [3,4] may be processed.

In another instance, determining whether a subset of CAN payload datasatisfies the first correlation relationship may include processing aplurality of reverse ordered bytes in same byte positions of the CANpayload data in each slot of the rolling buffer. The same byte positionsmay include any byte positions [0] to [7]. Some examples of a pluralityof reversed ordered bytes that may be processed include bytes in thefollowing byte positions: [1,0], [2,1], [3,2], [4,3], [5,4], [6,5],[7,6], [2,1,0], [3,2,1], [4,3,2], [5,4,3], [6,5,4], [7,6,5], amongothers.

For example, monitoring device 402 processes subset 813, shown in FIG.8F, for determining whether subset 813 meets the second criterion.Subset 813 includes two ordered bytes of CAN payload data in a same byteposition, position [4,3].

For instance, monitoring device 402 processes subset 813 for determiningthe relative increase between the following consecutive pairs of tworeverse ordered bytes in positions [4,3] in rolling buffer 800: ([807ge, 807 gd] and [807 fe, 807 fd]), ([807 fe, 807 fd] and [807 ee, 807ed]), ([807 ee, 807 ed] and [807 de, 807 dd]), ([807 de, 807 dd] and[807 ce, 807 cd]), ([807 ce, 807 cd] and [807 be, 807 bd]), and ([807be, 807 bd] and [807 ae, 807 ad]). Next, monitoring device 402 thendetermines whether the relative increase between the consecutive pairsof the reverse ordered bytes exceeds the second predefined threshold,20%.

Shown in FIG. 9D is table 914 comprising exemplary bytes in position[4,3] presently stored in rolling buffer 800. Table 914 includes thevalues of bytes [807 ge, 807 gd] to [807 ae, 807 ad] in Hex 915 and Dec916. Also included in table 914 is an example of the relative increase917 between the consecutive pairs of reverse ordered bytes in position[4,3] in the rolling buffer 800 determined by monitoring device 402. Inthis example, the relative increase between each consecutive pair ofreverse ordered bytes in position [4,3] exceeds the second predefinedthreshold 20% indicating that subset 813 meets the second criterion. Assuch, subset 813 corresponding to CAN ID 0x400, byte positions [4,3],may be indicate a candidate for target data.

In the present example, since subset 813 meets the second criterion,subprocess 700 proceeds to block 707. However, if subset 813 did notmeet the second criterion subprocess 700 would proceed to block 708.

Additionally, and/or alternatively, one or more subsets comprised of tworeversed ordered bytes in other byte positions of CAN payload data,other than positions [4,3] may be processed.

The example above describes target data, i.e., undefinedmanufacturer-specific CAN data, as fuel rate data and first referencedata as engine load data for descriptive purposes only. Target data maybe any vehicle variable-related data and first reference data may alsobe any vehicle variable-related data having a correlation relationshipwith the target data. Specific and non-limiting examples of target datainclude, odometer data and speed data, e.g., speed data included inmanufacturer-specific CAN data.

The subsets of CAN payload data evaluated to meet the second criteriondescribed in the examples above are provided for explanation purposesonly and embodiments are not intended to be limited to the examplesdescribed herein.

At block 707, subprocess 700 may include incrementing a second counterif a subset of CAN payload data meets the second criterion. A secondcounter indicates the total number of instances a subset correspondingto a specific byte position(s) satisfies the first correlationrelationship. If a subset of undefined CAN payload meets the secondcriterion, an indication of the byte position(s) of that subset, and asecond counter associated therewith, is stored for future use.Subprocess 700 then proceeds to block 708.

For example, as described hereinabove, subset 811 corresponding to byteposition [0] of CAN payload data meets the second criterion.Accordingly, monitoring device 402 increments secondcounter[0] by 1 andstores first subset data indicating byte position [0] andsecondcounter[0], for example, in datastore 506 of monitoring device402.

A conceptual diagram of exemplary first subset data 1001 is shown inFIG. 10A. In this example, first subset data 1001 a indicates byteposition [0] and associated secondcounter[0], 3. For instance, firstsubset data 1001 a indicates that a data byte in position[0] of CANpayload data corresponding to a first CAN ID, e.g., 0x400, has met thesecond criterion 3 times.

First subset data 1001 b indicates byte positions [3,4] and associatedsecondcounter[3,4], 5. For instance, first subset data 1001 b indicatesthat data bytes in positions [3,4] of CAN payload data corresponding toa first CAN ID, e.g., 0x400, has met the second criterion 5 times.

Finally, first subset data 1001 c indicates byte positions [4,3] andassociated secondcounter[4,3], 44. For instance, first subset data 1001c indicates that a data bytes in position[4,3] of CAN payload datacorresponding to a first CAN ID, e.g., 0x400, has met the secondcriterion 44 times. Monitoring device 402 may store first subset data1001 in datastore 506 or other datastore of monitoring device 402.

At block 708, subprocess 700 may include determining whether allsubsets, from a group predefined subsets, of CAN payload data has beenprocessed for identifying one or more subsets of the CAN payload datasatisfying the first correlation relationship. In the event there areother subsets still to be processed, the loop of blocks 706 to 708 willbe repeated. Otherwise subprocess 700 will proceed to the next block.

An exemplary group of predefined subsets is shown in table 1002 of FIG.10B. At block 708, monitoring device 402 determines whether all subsetsin table 1002 have been processed. If so, subprocess 700 proceeds to thenext block. Otherwise subprocess 700 returns to block 706.

At block 710, subprocess 700 may include comparing the first counter toa first counting threshold. The first counter not exceeding the firstcounting threshold indicates that the number of instances of valid testconditions for evaluating whether the first reference data and CANpayload data satisfy the first correlation relationship is insufficient.Should the first counter exceed the first counting threshold subprocess700 proceeds to block 711. Otherwise subprocess 700 returns to block 702

An exemplary first counting threshold is 49. In the present example thefirst counter is 50 indicating that there were 50 instances of validtest conditions for evaluating whether the first reference data and CANpayload data satisfy the first correlation relationship. As the firstcounter 50 exceeds the first counting threshold 49, subprocess 700proceeds to the next block.

Next, at block 711, subprocess 700 includes comparing one or more secondcounters with a second counting threshold. A second counting thresholdindicates a minimum number of instances a subset must satisfy the firstcorrelation relationship to be a candidate for target data. If a secondcounter exceeds the second counting threshold, subprocess 700 proceedsto block 712, otherwise subprocess 700 proceeds to block 714A and iscomplete.

An exemplary second counting threshold is 39. In the present example,monitoring device 402 processes first subset data 1001 to determine ifone or more of secondcounter[0], secondcounter[3,4] andsecondcounter[4,3], exceeds the second counting threshold. Monitoringdevice 402 determines secondcounter[4,3], exceeds the second countingthreshold 39. Accordingly, subprocess proceeds to block 712. However, ifnone of the second counters exceeded the second count threshold,subprocess 700 would proceed to block 714A and be complete.

At block 712, subprocess 700 forms first position data based on firstsubset data having a second counter exceeding the second countingthreshold.

For example, secondcounter[4,3] of position data 1001 c exceeds thesecond counting threshold. Monitoring device 402 forms first positiondata 1003, as shown in FIG. 10C, based on first subset data 1001 c. Forinstance, first position data 1003 indicates subset position [4,3] andassociated secondcounter[4,3], 44.

Next, at block 713, subprocess 700 forms first candidate data based onthe first position data and the first CAN ID. The first candidate dataprovides an indication of a first candidate for target data. In someinstances, first candidate data may also include an indication of thesecond counter. Still at block 713, subprocess 700 may include providingfirst candidate data to a second subprocess for further processing, suchas, subprocess 601.

In the present example, monitoring device 402 forms first candidate databased on first position data 1003 and first CAN ID 0x400. For instance,first candidate data 1004, shown in FIG. 10D, indicates a candidate ofthe target data in byte position [4,3] of an undefined CAN payloadcorresponding to CAN ID 0x400. In some instances, first candidate data1004 may include an indication of secondcounter[4,3], 44, as shown.

In some instances, monitoring device 402 may transmit first candidatedata 1004 to remote server 404 via communication network 406 for futureuse.

One of ordinary skill will appreciate that a plurality of candidatescorresponding to a same first CAN ID may be identified. For instance, ifsecondcounter[3,4] of position data 1001 b exceeded the second countingthreshold, first candidate data may also indicate another candidate ofthe target data in byte position [3,4] of an undefined CAN payloadcorresponding to CAN ID 0x400.

Finally, at block 714A subprocess 700 is complete.

Target data, first reference data and first correlation relationshipdescribed in the examples described above are provided for explanationpurposes only. Similarly, other first criterion and/or other secondcriterion indicative if the first correlation relationship may be used.Embodiments are not intended to be limited to the examples describedherein.

In some instances, CAN messages corresponding to a selected first CAN IDare not transmitted on the CAN bus. In such instances, subprocess 700may timeout and proceed directly to block 714A.

Subprocess 700′

Illustrated in FIG. 7B is a simplified flow diagram of anothersubprocess 700′ for identifying one or more candidates for target dataaccording to an embodiment. Subprocess 700′ may include identifyingcandidates based on a first correlation relationship between a targetdata and a first reference data.

The functionality of blocks of subprocess 700′ to be described below arethe same and/or substantially similar to blocks of subprocess 700 andthe previous description of the latter can be applied to the former withthe exceptions as described below.

In subprocess 700′, block 714A of subprocess 700 is replaced with block714B.

At block 714B, subprocess 700′ includes determining whether there isother CAN payload data corresponding to another first CAN ID of thegroup of available CAN IDs to be processed. If so, subprocess 700′returns to block 701A, otherwise, subprocess 700′ proceeds to block 714Band is complete.

For example, monitoring device 402 determines whether CAN payload datacorresponding to another first CAN ID in the group of available CAN IDscomprising 0x001 to 0x7FF, is still to be processed. If this is thecase, subprocess 700 returns to block 701A wherein another first CAN IDis selected, for instance, 0x689.

In some instances, CAN messages corresponding to a selected first CAN IDare not transmitted on the CAN bus. In such instances, subprocess 700′may timeout and proceed directly to block 714B.

Subprocess 1100

Illustrated in FIG. 11 is a simplified flow diagram of a subprocess 1100for identifying one or more candidates for target data according to anembodiment. Subprocess 1100 may include identifying candidates based ona first correlation relationship between target data and first referencedata, and a second correlation relationship between target data andfirst reference data.

In a present example, a target data may be in the form of fuel rate dataand first reference data may be in the form of engine load data. Anexemplary first correlation relationship between fuel consumption andengine load may be characterized as an increase in engine loadcorrelates to an increase in fuel consumption. An exemplary secondcorrelation relationship between fuel consumption and engine load may becharacterized as a constant engine load correlates to constant fuelconsumption.

The functionality of blocks of subprocess 1100 to be described below arethe same and/or substantially similar to blocks of subprocesses 700 and700′, and the previous description of the latter can be applied to theformer with the exceptions as described below.

Subprocess 1100 begins at block 701A and proceeds therefrom to block701B. From block 701B, subprocess 1100 diverges along two paths, A andB.

Referring to path A, subprocess 1100 proceeds to block 790 comprisingblocks 702 to 710 via interface 720, as shown. Functionality of blocks702 to 710 are described above with reference to subprocesses 700 inFIG. 7A.

At block 790, subprocess 1100 includes identifying candidates based onthe first correlation relationship between target data and firstreference data, by forming, for example, first subset data 1001 in FIG.10A. When the first counter exceeds the first counting threshold,subprocess 1100 proceeds to block 1111 via interface 721 of block 790.

Referring now to path B, at block 1102, subprocess 1100 may includemonitoring the rolling buffer and, upon receipt of new first referencedata and new CAN payload data, subprocess 1100 proceeds to block 1104.

For example, monitoring device 402 monitors rolling buffer 800 and uponstorage of new engine load data 804 g and CAN payload data 807 g, forexample in slot 1, subprocess 1100 proceeds to the next block.

At block 1104, subprocess 1100 may include determining whether the firstreference data stored in the rolling buffer provides a valid testcondition for evaluating whether the first reference data and CANpayload data satisfy the second correlation relationship.

A specific and non-limiting example of a method for determining whetherthe first reference data provides a valid test condition is bydetermining whether the first reference data meets a third criterionindicative of the second correlation relationship.

An exemplary third criterion may be engine load represented by engineload data 804 in each slot of rolling buffer 800 must be within apredefined value of the average thereof. An exemplary predefined valueis 1.

Referring now to FIG. 12A, shown is table 1201 comprising exemplaryengine load data 804 a-804 g presently stored in rolling buffer 800.Table 1201 includes the value of engine load data 804 a-804 g in Hex1202 and in Dec 1203, and engine load 1204 calculated as per dataconversion rule, engine load=(Dec*100/255). Engine load 1204 representsa percentage of load on an engine and may range between [0-100%].

In the present example, monitoring device 402 calculates the actualengine load 1204 using the data conversion rule described hereinaboveand the average engine load 1220 to be 4.7%. Next, monitoring devicedetermines the absolute difference 1205 between an engine load 1204 andthe average engine load 1220, as shown in table 1201.

For example, engine load data 804 g in slot 1 indicates an engine loadof 3.92%. The absolute difference 1205 between engine load 1204indicated by engine load data 804 g and average engine load 1220, 4.7%,is 0.78, (i.e., 13.92−4.71=0.78).

Monitoring device 402 determines whether the difference 1205 betweenengine load 1204 represented by engine load data 804 in each slot ofrolling buffer 800 is within 1 of the average engine load 1220, 4.7%. Inthis example, the difference 1205 of the average engine load 1204 andengine load data 804 in each slot is within 1, indicating engine loaddata 804 meets the third criterion.

Still at block 1104, subprocess 1100 may include incrementing a thirdcounter provided the first reference data meets the third criterion. Thethird counter indicates the total number of instances first referencedata provides a valid test condition for evaluating whether the firstreference data and CAN payload data satisfy the second correlationrelationship. If first reference data provides a valid test conditionfor evaluating whether the first reference data and CAN payload datasatisfy the second correlation relationship, subprocess 1100 proceeds toblock 1106, otherwise, subprocess 1100 proceeds to block 1102.

In the present example, engine load data 804 met the third criterionindicating engine load data 804 provided a valid test condition forevaluating whether the engine load data 804 and CAN payload data satisfythe second correlation relationship. Thus, monitoring device 402incremented a third counter by 1 and subprocess 1100 proceeded to block1106.

The third criterion described in this example is provided forexplanation purposes only and embodiments are not intended to be limitedto the examples described herein.

Next, subprocess 1100 proceeds to block 1106. The functionality of block1106 to be described below is substantially similar to block 706 and theprevious description of the latter can be applied to the former with theexceptions as described below.

At block 1106, subprocess 1100 may include processing CAN payload datafor identifying one or more subsets of the CAN payload data satisfyingthe second correlation relationship. If one or more of the subsetssatisfies the second correlation relationship, subprocess 1100 proceedsto block 1107, otherwise subprocess returns to block 1102.

Shown in FIG. 8E, is a conceptual diagram of CAN payload data 807 g to807 a presently stored in slots 1 to 7, respectively, of rolling buffer800. For instance, CAN payload data 807 g in slot 1 includes byte 807 gain byte position [0], 807 gb in byte position [1], 807 gc in byteposition [2], 807 gd in byte position [3], 807 ge in byte position [4],807 gf in byte position [5], 807 gg in byte position [6], and 807 gh inbyte position [7], as indicated in FIG. 8E. Similarly, CAN payload data807 f in slot 2 comprises bytes 807 fa to 807 fh corresponding to bytepositions [0] to [7], respectively, and so forth.

Target data may be comprised of one or more bytes in any byte positions[0] to [7] of an undefined CAN message payload. Accordingly, processingCAN payload data for determining one or more subsets of the CAN payloaddata that satisfies the first correlation relationship may includeprocessing a plurality of subsets of data of CAN payload data in anybyte position(s) [0] to [7].

A specific and non-limiting example of a method for determining whetherone or more subsets of the CAN payload data satisfies the secondcorrelation relationship may include determining whether the one or moresubsets of the CAN payload data meets a fourth criterion indicative ofthe second correlation relationship. An exemplary fourth criterion maybe the relative difference between CAN payload data 807 in each slot ofrolling buffer 800 and average thereof must not exceed a thirdpredefined threshold, for instance, 50%.

In the present example, monitoring device 402 processes subset 811,shown in FIG. 8E for determining whether subset 811 meets the fourthcriterion.

Referring now to FIG. 12B, shown is table 1206 comprising exemplarybytes 804 ga-804 aa presently stored in rolling buffer 800. Table 1206includes exemplary values of bytes 804 ga-804 aa in Hex 1207 and Dec1208.

In this example, monitoring device 402 determines the average 1222 valueof bytes 804 ga-804 aa to be 207 and the percentage difference 1210between the value of CAN payload data bytes 804 ga-804 aa and theaverage 1222 thereof, as shown in table 1206. For instance, the decimalvalue of CAN payload data byte 807 ga in slot 1 is 170. The percentagedifference between average 1222, 207 and decimal value of CAN payloaddata byte 807 ga 170 is 22%, (i.e., (207−170)/207=22%).

In this example, the relative difference between CAN payload data bytes807 ga-807 aa and the average 1222 thereof, 207 does not exceed thethird predefined threshold, 50%, indicating that subset 811 meets thefourth criterion. As such, subset 811 corresponding to CAN ID 0x400,byte position [0], may be a candidate for target data.

In the present example, since subset 811 meets the fourth criterion,subprocess 1100 proceeds to block 1107. However, if subset 811 did notmeet the fourth criterion subprocess would proceed to block 1108.

Additionally, and/or alternatively, a subset may comprise one or morebytes, in one or more byte positions [0] to [7], of CAN payload data.

The third criterion, fourth criterion and subsets of CAN payload datadescribed in this example are provided for explanation purposes only.Embodiments are not intended to be limited to the examples describedherein.

At block 1107, subprocess 1100 may include incrementing a fourth counterif a subset of CAN payload data meets the fourth criterion. A fourthcounter indicates the total number of instances a subset correspondingto a specific byte position(s) satisfies the second correlationrelationship. If a subset of undefined CAN payload meets the fourthcriterion, an indication of the byte position(s) of that subset, and afourth counter associated therewith, is stored for future use.Subprocess 1100 then proceeds to block 1108.

For example, as described hereinabove, subset 811 corresponding to byteposition [0] of CAN payload data meets the fourth criterion.Accordingly, monitoring device 402 increments fourthcounter[0] by 1 andstores second subset data indicating byte position [0] andfourthcounter[0], for example, in datastore 506 of monitoring device402.

A conceptual diagram of exemplary second subset data is 1301 shown inFIG. 13A. In this example, second subset data 1301 a indicates byteposition [0] and associated fourthcounter[0], 10. For instance, secondsubset data 1301 a indicates that a data byte in position[0] of CANpayload data corresponding to a first CAN ID, e.g., 0x400, has met thefourth criterion 10 times.

Second subset data 1301 b indicates byte position [5,6] and associatedfourthcounter[5,6], 4. For instance, second subset data 1301 b indicatesthat a data bytes in position[5,6] of CAN payload data corresponding toa first CAN ID, e.g., 0x400, has met the fourth criterion 4 times.

Finally, second subset data 1301 c indicates byte position [4,3] andassociated fourthcounter[4,3], 47. For instance, second subset data 1301c indicates that a data bytes in position[4,3] of CAN payload datacorresponding to a first CAN ID, e.g., 0x400, has met the fourthcriterion 47 times.

Next, at block 1108, subprocess 1100 may include determining whether allsubsets, from a group of predefined subsets, of CAN payload data hasbeen processed for identifying one or more subsets of the CAN payloaddata satisfying the second correlation relationship. In the event thereare other subsets still to be processed, the loop of blocks 1106 to 1108will be repeated. Otherwise subprocess 1110 will proceed to the nextblock.

An exemplary group of predefined subsets is shown in table 1302 of FIG.13B. At block 1108, monitoring device 402 determines whether all subsetsin table 1202 have been processed. If so, subprocess 1100 proceeds tothe next block. Otherwise subprocess 1100 returns to block 106.

At block 1110, subprocess 1100 may include comparing the third counterto a third counting threshold. The third counter not exceeding the thirdcounting threshold indicates that the number instances of valid testconditions for evaluating whether the first reference data and CANpayload data satisfy the second correlation relationship isinsufficient. Should the third counter exceed the third countingthreshold, subprocess 1100 proceeds to block 1111. Otherwise, subprocess1100 returns to block 1102.

An exemplary third counting threshold is 49. In the present example thethird counter is 50, indicating that there were 50 instances of validtest conditions for evaluating whether the first reference data and CANpayload data satisfy the second correlation relationship. As the thirdcounter 50 exceeds the first counting threshold 49, subprocess 1100proceeds block 1111.

At block 1111, path A and path B merge, and subprocess 1100 may includecomparing one or more second counters with a second counting threshold.A second counting threshold indicates a minimum number of instances asubset must satisfy the first correlation relationship to be a possiblecandidate for target data. Subprocess 1100 further includes comparingone or more fourth counters with a fourth counting threshold. A fourthcounting threshold indicates a minimum number of instances a subset mustsatisfy the second correlation relationship to be a possible candidatefor target data. Should one or more second counters and one or morefourth counters exceed the second counting threshold and fourth countingthreshold, respectively, subprocess 1100 proceeds to block 1112,otherwise, subprocess 1100 proceeds to block 1114.

An exemplary second counting threshold is 39. In the present example,monitoring device 402 processes first subset data 1001 to determine ifone or more of secondcounter[0], secondcounter[3,4] andsecondcounter[4,3], exceeds the second counting threshold. Monitoringdevice 402 determines secondcounter[4,3], exceeds the second countingthreshold 39. However, if none of the second counters exceeded thesecond count threshold, subprocess 1100 would proceed to block 1114.

An exemplary fourth counting threshold is 39. In the present example,monitoring device 402 processes second subset data 1301 to determine ifone or more of fourthcounter[0], fourthcounter[5,6] andfourthcounter[4,3], exceeds the fourth counting threshold. Monitoringdevice 402 determines fourthcounter[4,3], 47, exceeds the fourthcounting threshold 39. However, if none of the fourth counters exceededthe fourth count threshold, subprocess 1100 would proceed to block 1114.

As secondcounter[4,3], 44, exceeds the second counting threshold 39 andfourthcounter[4,3], 47, exceeds the fourth counting threshold 39,subprocess 1100 proceeds to block 1112.

At block 1112, subprocess 1100 forms first position data based on firstsubset data having a second counter exceeding the second countingthreshold and forms second position data based on second subset datahaving a fourth counter exceeding the fourth counting threshold.

In the present example, monitoring device 402 forms first position data1003 indicating a possible candidate at position [4,3] of CAN payloaddata and second position data 1303 indicating a possible candidate atposition [4,3] of CAN payload data. Exemplary second position data 1303is shown in FIG. 13C. Optionally, first position data 1003 and secondposition data 1303 may also indicate associated second counter, 44, andfourth counter 47, as shown.

Next, at block 1113, subprocess 1100 includes processing first positiondata and second position data to determine if each thereof indicate asame byte position. If so, subprocess 1100 also includes forming firstcandidate data indicative of that same byte position and the first CANID. Optionally, first candidate data may indicate the second counter andfourth counter associated with the same byte position. Optionally, atblock 1113 subprocess 1100 may provide the first candidate data toanother subprocess.

For example, monitoring device 402 processes first position data 1003and second position data 1303 and determines that both thereof indicatea possible candidate at a same byte position [4,3]. FIG. 13D showsexemplary first candidate data 1304 formed by monitoring device 402indicating same byte position [4,3] and first CAN ID 0x400. Firstcandidate data 1304 may also indicate a second counter and fourthcounter associated with byte position [4,3] as shown.

In some instances, monitoring device 402 may transmit first candidatedata 1304 to remote server 404 via communication network 406 for futureuse.

One of ordinary skill will appreciate that a plurality of candidatescorresponding to a same first CAN ID may be identified. For instance, ifsecondcounter[0] of position data 1001 b exceeded the second countingthreshold, and fourthcounter[0] also exceeded the fourth countingthreshold, first candidate data may also indicate another candidate ofthe target data in byte position [0] of an undefined CAN payloadcorresponding to CAN ID 0x400.

Finally, at block 1114, subprocess 1100 includes determining whetherthere is other CAN payload data corresponding to another first CAN ID ofthe group of available CAN IDs to be processed. If so, subprocess 1100returns to block 701A, otherwise, subprocess 1100 is complete.

For example, monitoring device 402 determines whether CAN payload datacorresponding to another first CAN ID in the group of available CAN IDscomprising 0x001 to 0x7FF, is still to be processed. If this is thecase, subprocess 1100 returns to block 701A wherein another first CAN IDis selected, for instance, 0x689.

In some instances, CAN messages corresponding to the selected first CANID are not transmitted on the CAN bus. In such instances, subprocess1100 may timeout and proceed directly to block 1114.

Target data, first reference data, first correlation relationship andsecond correlation relationship described in this example are providedfor explanation purposes only. Similarly, third criterion and/or fourthcriterion described in this example are provided for explanationpurposes only. Embodiments are not intended to be limited to theexamples described herein.

Subprocess 1400

Illustrated in FIG. 14 is a simplified flow diagram of anothersubprocess 1400 for identifying one or more candidates for target dataaccording to an embodiment. Subprocess 1400 may include determiningfirst candidates based on a first correlation relationship betweentarget data and first reference data and a second correlationrelationship between target data, first reference data and secondreference data.

In a present example, target data may be in the form of fuel rate data,first reference data may be in the form of engine load data and secondreference data may be in the form of speed data. An exemplary firstcorrelation relationship between fuel consumption and engine load may becharacterized as an increase in engine load correlates to an increase infuel consumption. An exemplary second correlation relationship betweenfuel consumption, engine load and speed may be characterized as constantengine load and constant speed correlates to constant fuel consumption.

The functionality of blocks of subprocess 1400 to be described below aresubstantially similar and/or the same to blocks of subprocess 1100 andthe previous description of the latter can be applied to the former withthe exceptions as described below.

Blocks 701B, 1102, and 1104 of subprocess 1100 are replaced with blocks1401, 1402 and 1404 respectively, in subprocess 1400.

Subprocess 1400 begins at block 701A and proceeds therefrom to block1401. The functionality of block 1401 to be described below issubstantially similar to block 701B and the previous description ofblock 701A can be applied to the former with the exceptions as describedbelow.

At block 1401, in addition to collecting and storing a plurality offirst reference data and a plurality of CAN payload data from a CAN busand storing that data in a rolling buffer of size S, subprocess 1400also includes collecting and storing a plurality of second referencedata from the CAN bus and storing the plurality of second reference datain the same rolling buffer.

In some instances, first reference data, second reference data and CANpayload data are collected and stored at predefined intervals. Once allS slots of the rolling buffer are filled, subprocess 1400 proceeds tothe next blocks. Notwithstanding subprocess 1400 proceeding to the nextblocks, samples of first reference data, second reference data, and CANpayload data may continue to be collected and stored in the rollingbuffer at predefined intervals.

Shown in FIG. 15A is a conceptual diagram of the contents of rollingbuffer 800′ of size 7. In this example monitoring device 402 hascollected first reference data in the form of engine load data 804,undefined payload data 807 corresponding to first CAN ID 0x400, andsecond reference data in the form of speed data 1504. For instance,rolling buffer 800′ comprises engine load data 804 g to 804 a in slots 1to 7, CAN payload data 807 g to 807 a in slots 1 to 7, and speed data1507 g to 1500 a in slots 1 to 7, respectively.

In this example, rolling buffer 800′ is size 7, however, a rollingbuffer may be any size.

For descriptive purposes, first reference data, second reference data,and CAN payload data are described to be collected at a predefinedinterval of 1 second. In practise, however, first reference data, secondreference data, and CAN payload data may be collected at anotherpredefined interval.

Alternatively, each of the plurality of second reference data iscollected at a time temporally proximate a time CAN payload data iscollected and first reference data is collected. For example, CANpayload data may be collected at the same time as, or at a time closeto, the time first reference data and the time second reference data iscollected.

From block 1401, subprocess 1400 diverges along two paths, A and B.

Referring to path A, subprocess 1400 proceeds to block 790 comprisingblocks 702 to 710 via interface 720, as shown. The series of steps inblock 790 as previously described with reference to FIG. 7A, andassociated rolling buffer 800, are the same with reference to firstreference data 804 and CAN payload data 807.

For example, the series of steps in block 790 as previously describedwith reference to FIG. 7A and rolling buffer 800 are the same withreference to the first column 1501 of rolling buffer 800′ comprisingfirst reference data 804 and 2nd column 1502 of rolling buffer 800′comprising CAN payload data 807.

At block 790, subprocess 1400 includes identifying candidates based onthe first correlation relationship between target data and firstreference data, by forming, for example, first subset data 1001 in FIG.10A. When a first counter exceeds the first counting threshold,subprocess 1400 proceeds to block 1111 via interface 721 of block 790.

Referring now to path B, at block 1402, subprocess 1400 may includemonitoring the rolling buffer and, upon receipt of new first referencedata, new CAN payload data, and new second reference data, subprocess1400 proceeds to the next block.

For example, monitoring device 402 monitors rolling buffer 800′ and uponstorage of new engine load data 804 g, new CAN payload data 807 g, andnew speed data 1507 g, for example in slot 1, subprocess 1400 proceedsto block 1404.

At block 1404, subprocess 1400 may include determining whether the firstreference data and the second reference data provide a valid testcondition for evaluating whether the first reference data, secondreference data and CAN payload data satisfy a second correlationrelationship.

A specific and non-limiting example of a method for determining whetherthe first reference data and second reference data provide a valid testcondition is by determining whether the first reference data and secondreference data meets a fifth criterion and sixth criterion,respectively, indicative of the second correlation relationship.

An exemplary fifth criterion may be engine load represented by engineload data 804 in each slot of rolling buffer 800′ must be within apredefined value of the average thereof, An exemplary predefined valueis 1. An exemplary sixth criterion may be speed represented by speeddata 1507 in each slot of rolling buffer 800′ must be within apredefined value of the average thereof, for example, 2 km/hr.

Referring again to FIG. 12A, shown is table 1201 comprising exemplaryengine load data 804 a-804 g presently stored in rolling buffer 800.Table 1201 also includes the difference 1205 between engine load 904 andthe average engine load 1220 as determined by monitoring device 402. Asengine load 1204 represented by engine load data 804 in each slot ofrolling buffer 800 is within 1 of the average engine load 1220, 4.7%,engine load data 804 meets the fifth criterion.

Referring now to FIG. 15B, shown is table 1510 comprising exemplaryspeed data 1507 a-1507 g presently stored in rolling buffer 800′. In thepresent example, monitoring device 402 calculates the speed 1513indicated by speed data 1507 and the average speed 1520, 110 km/hr.Next, monitoring device 402 determines the difference 1514 between speed1513 and average speed 1520, as shown in table 1510. As the difference1514 is within 2 km/hr of the average speed, speed data 1507 meets thesixth criterion.

Still at block 1404, subprocess 1400 may include incrementing a thirdcounter if the first reference data meets the fifth criterion and thesecond reference data meets the sixth criterion. In this example, thethird counter indicates the total number of instances first referencedata and second reference data provides a valid test condition forevaluating whether the first reference data, second reference data andCAN payload data satisfy the second correlation relationship.

If the first reference data and the second reference data provide avalid test condition for evaluating whether the first reference data,second reference data and CAN payload data satisfy the secondcorrelation relationship, subprocess 1400 proceeds to block 1106,otherwise, subprocess 1400 returns to block 1402.

In other embodiments for identifying one or more candidates for targetdata according to an embodiment. Subprocess 1400 may include determiningfirst candidates based on a first correlation relationship betweentarget data and first reference data and a second correlationrelationship between target data, first reference data and secondreference data.

In some embodiments of subprocesses for identifying one or morecandidates for target data may include determining first candidatesbased on one or more correlation relationships between target data andone or more reference data. Some specific and non-limiting examplesinclude, determining first candidates based on a first reference data,second reference data and target data satisfying a first correlationrelationship; determining first candidates based on a first referencedata, second reference data, third reference data and target datasatisfying a second correlation relationship; determining firstcandidates based on a first reference data, second reference data, andtarget data satisfying a second correlation relationship and at least athird reference data and target data satisfying a third correlationrelationship. Other correlation relationships between target data andvarious reference data for identifying one or more candidates for targetdata may be envisioned. Numerous other embodiments of the invention willbe apparent to persons skilled in the art without departing from thescope of the invention as defined in the appended claims.

The example above describes target data, i.e., undefinedmanufacturer-specific CAN data, as fuel rate data, first reference dataas engine load data, and second reference data as speed data forillustrative purposes only. However, target data may be any vehiclevariable-related data, first reference data and second reference datamay also be any vehicle variable-related data. Specific and non-limitingexamples of target data include, odometer data and speed data, e.g.,speed data included in manufacturer-specific CAN data.

Target data, first reference data, second reference data, first andsecond correlation relationships described in the examples above are forexplanation purposes only and embodiments are not intended to be limitedto the examples described herein. Target data may include anyvehicle-related transmitted on a CAN bus.

Subprocess 1600

Shown in FIG. 16 is a simplified flow diagram of subprocess 1600 foridentifying manufacturer-specific CAN data, i.e., target data, for afirst vehicle type according to an embodiment. Starting at block 1602,subprocess 1600 may include receiving a plurality of first candidatedata from a plurality of first processes, for example, subprocesses 700,700′, 1100, 1400, 2100, 2500, 2700, and 2900.

In a first example, target data may be in the form of fuel rate data anda vehicle type may be in the form of a 2020 Toyota Corolla.

In this example, monitoring devices 402 of telematics system 400 mayeach transmit a plurality of first candidate data to remote server 404via communication network 406. Shown in FIG. 17A is a conceptual diagramof exemplary first candidate data 1700 received by remote server 404.First candidate data 1700 may be stored in a datastore TBD of remoteserver 404 or other datastore.

Firstly, at block 1604, subprocess 1600 includes associating a vehicletype with each first candidate data of the plurality of first candidatedata received.

For example, remote server 404 associates first candidate data 1701 ofthe plurality of first candidate data 1700 with a vehicle type ID 6002corresponding to a vehicle type, as shown in FIG. 17A. Vehicle type ID6002 indicates a vehicle type of vehicle 408 associated with eachmonitoring device 402. Remote server 404 may have previously receiveddata indicating a vehicle type associated with each monitoring device402.

In this example, vehicle types are defined by vehicle make, model andyear. Exemplary vehicle type IDs are provided in table 1720 in FIG. 17B.For instance, vehicle type ID 5674 corresponds to a vehicle type definedas a 2017 Toyota Corolla. In this example, each first candidate data1701 of the plurality of first candidate data 1700 indicates a firstcandidate for fuel rate data for a vehicle type.

Next, at block 1606, subprocess 1600 includes selecting a subset offirst candidate data corresponding to a first vehicle type for formingsecond candidate data. Second candidate data indicates candidates fortarget data for the first vehicle type.

For example, remote server 404 selects a subset of first candidate data1700 corresponding to vehicle type ID 6002 associated with vehicle type2020 Toyota, Corolla to form exemplary second candidate data 1730, shownin FIG. 17C. Second candidate data 1730 indicates two possiblecandidates for target data, i.e., fuel rate data. In particular, a firstcandidate in byte position [4,3] of CAN payload data corresponding toCAN ID 0x400 and a second candidate in byte position [0,1] of CANpayload data corresponding to CAN ID 0x022.

Next, at block 1608, subprocess 1600 processes second candidate data todetermine which of the first candidates indicated thereby is likely toindicate target data associated with the first vehicle type.

In a first example, remote server 402 may process second candidate data1730 to determine the most likely first candidate by selecting the firstcandidate that is indicated in the greatest number of instances thereof.For instance, a first candidate corresponding to byte position [4,3] andCAN ID 0x400 is indicated in six instances out of seven instances.Whereas a first candidate corresponding to byte position [0,1] and CANID 0x022 is indicated once out of seven instances.

Alternatively, remote server 402 may process second candidate data 1730and other data for determining the most likely first candidate. Forexample, data indicative of a counter related to a first candidate maybe included in first candidate data. In such instances, remote server402 may process second candidate data 1730 and data indicative of acounter related to a first candidate data for determining the mostlikely first candidate.

In this example, remote server 404 identifies fuel rate data for a 2020Toyota Corolla as data in byte position [4,3] of CAN payload datacorresponding to CAN ID 0x400.

Finally, at block 1608, subprocess 1600 generates identification datacorresponding to the identity of the manufacturer-specific CAN data forthe first vehicle type, the identification data indicative of amanufacturer-specific CAN data byte position and correspondingmanufacturer-specific CAN data CAN ID associated with the secondcandidate data. In other words, identification data provides anindication of a byte position(s) and CAN ID corresponding to the targetdata, i.e. manufacturer-specific CAN data.

For example, remote server 404 generates identification data forproviding thereof to a fleet manager. In the present example, remoteserver 404 may indicate to a fleet manager that fuel rate data for a2020 Toyota Corolla is located at byte positions [4,3] of CAN payloaddata corresponding to CAN ID 0x400. Shown in FIG. 17D is a conceptualdiagram of exemplary identification data indicating fuel rate data for a2020 Toyota Corolla that may be provided by remote server 404 to a fleetmanager.

Alternatively, and/or additionally, identification data is stored, forexample, in a datastore of the remote server 404, for future usethereby.

Process 1800

Now referring to FIG. 18 , shown is a simplified flow diagram of aprocess 1800 for collecting manufacture-specific CAN data for at least afirst vehicle type according to an embodiment.

Process 1800 includes a plurality of subprocesses 1800A and a subprocess1800B. Subprocess 1800 and subprocess 1800B are described further belowwith reference to FIGS. 18, 19, 20A, and 20B.

Shown in FIG. 19 is another simplified diagram of exemplary telematicssystem 400 including remote server 404 communicatively coupled tomonitoring devices 402 a, 402 b and 402 c via communication network 406.

Subprocess 1800A

Beginning at block 1801, subprocess 1800A includes collecting vehicleCAN data based on definition data. Definition data includes definitionsdefining CAN payload data bytes and CAN ID for vehicle CAN data to becollected. Subprocess 1800A is associated with a unique hardware ID(HWID) and a vehicle type of a plurality of vehicle types.

For instance, each of monitoring devices 402 a, 402 b, and 402 c, areassigned HWIDs 19402 a, 19402 b, 19402 c, respectively, and correspondto vehicle type IDs 5674, 6002 and 4628, respectively, indicative of avehicle type. In this example, monitoring device 402 is configured tocollect a plurality of vehicle CAN data from CAN bus 512. For instance,exemplary definition data 1902 stored, for example, in datastore 506,include definitions of a plurality of vehicle CAN data including CANpayload byte position(s) and corresponding CAN ID of vehicle CAN data tobe collected. In this example definition data 1902 indicates thatvehicle CAN data, engine load, speed and RPM are to be collected fromCAN payload data bytes [5,6] corresponding to CAN ID 0x1A7, CAN payloaddata bytes [2,3] corresponding to CAN ID 0x2B7 and CAN payload databytes [1,0] corresponding to CAN ID 0x33C, respectively.

In the present example, monitoring device 402 collects vehicle CAN data1904 including engine load data, speed data, and RPM data from CAN bus512 and stores vehicle CAN data 1904, for example, in datastore 506.

Next, at block 1802, subprocess 1800A includes providing collectedvehicle CAN data indicated to subprocess 1800B.

For example, each of monitoring devices 402 a, 402 b, and 402 c,transmits vehicle CAN data 1904 a,1904 b, and 1904 c, to remote sever404 via communication network 406.

At block 1803, subprocess 1800A includes determining first candidatesfor manufacturer-specific CAN data for forming first candidate data.

In the present example, manufacturer-specific data includes fuel data.

Referring now to FIG. 20A, shown is another simplified diagram ofexemplary telematics system 400 including remote server 404communicatively coupled to monitoring devices 402 a, 402 b and 402 c viacommunication network 406. In the present example, monitoring device 402follows steps described in one or more subprocesses including, 601, 700,700′, 1100, 1400, 2100, 2500, 2700 and 2900 for determining firstcandidates for manufacturer-specific CAN data. For example, each ofmonitoring devices 402 a, 402 b, and 402 c determines first candidatedata 2002 a, 2002 b, and 2002 c, as shown.

Next, at block 1804, subprocess 1800A includes providing first candidatedata to subprocess 1800B.

For example, each of monitoring devices 402 a, 402 b, and 402 c,transmits first candidate data 2002 a, 2002 b, and 2002 c to remotesever 404 via communication network 406.

At block 1805, subprocess 1800A includes determining whether instructiondata was provided by subprocess 1800B, instructing modification ofdefinition data to include a definition of manufacturer-specific CANdata. If so, subprocess 1800A proceeds to block 1805, otherwise,subprocess 1800A proceeds to block 1803.

For example, monitoring device 402 determines if it has receivedinstruction data from remote server 404 instructing definition data 1902to be modified to include a definition of manufacturer-specific CANdata.

According to an embodiment, instruction data may be received in the formof an instruction including definitions of manufacturer-specific CANdata.

For instance, monitoring devices 402 receives instruction data fromremote server 404 including instructions to modify definition data 1902to include definitions of manufacturer-specific CAN data, i.e., fueldata.

In a first example, monitoring devices 402 a, 402 b and 402 c receivesfirst instruction data including definitions of manufacturer-specificCAN data associated with vehicle type ID 5674. In this example,monitoring device 402 a associated with vehicle type ID 5674 determinesit has received instructions to modify definition data 1902. However,monitoring devices 402 b and 402 c associated with vehicle type IDs,6002 and 4628, ignore the instruction data as if it was never received.

In a second example, monitoring device 402 a receives first instructiondata including definitions of manufacturer-specific CAN data associatedwith vehicle type ID 5674, monitoring device 402 b receives secondinstruction data including definitions of manufacturer-specific CAN dataassociated with vehicle type ID 6002, and monitoring device 402 creceives third instruction data including definitions ofmanufacturer-specific CAN data associated with vehicle type ID 4628.

According to another embodiment, instruction data may be received in theform of second monitoring device instructions.

For example, upon receiving second monitoring device instructions,monitoring device 402 stores the second monitoring device instructionsin a non-transitory machine-readable storage medium, included in, forexample, datastore 506. The monitoring device instructions that whenexecuted cause processing resource 504 to, collect CAN payload datadefined by definition data, definition data indicative of definitions ofvehicle CAN data including a definition of manufacturer-specific CANdata associated with the at least a first vehicle type, and to transmitthe vehicle CAN data.

At block 1805, subprocess 1800A includes modifying definition data toinclude definitions of manufacturer-specific CAN data.

For example, provided each of monitoring devices 402 a, 402 b and 402 chave received instruction data to modify definition data 1902, anddefinition data 1902 is modified to include definition data 2005 a, 2005b, and 2005 b, corresponding to fuel data associated with vehicle typeIDs 5674, 6002 and 4628, respectively, as shown in FIG. 20B. FIG. 20B isyet another simplified diagram of exemplary telematics system 400.

Next, subprocess 1800A proceeds to block 1801.

In this example, monitoring devices 402 a, 402 b and 402 c, collectsvehicle data 1904 a, 1904 b and 1904 c, including fuel rate data 2006 a,2006 b and 2007 c according to definition data 1902, as shown in FIG.20B.

Next, at block 1802, subprocess 1800A includes providing collectedvehicle CAN data indicated by definition data 1902 to subprocess 1800B.

For example, each of monitoring devices 402 a, 402 b, and 402 c,transmits vehicle CAN data 1904 a, 1904 b and 1904 c, including fuelrate data 2006 a, 2006 b and 2007 c, respectively, to remote sever 404via communication network 406, as shown.

Subprocess 1800B

Subprocess 1800B begins at block 1806, including receiving a pluralityof CAN vehicle data from a plurality of subprocesses 1800A and providingan indication of CAN vehicle data associated with at least a HWID.

For example, remote server 404 receives CAN vehicle data 1904 a, 1904 band 1900 c from monitoring devices 402 a, 402 b and 402 c respectively,as shown in FIG. 19 . Remote server 404 then provides an indication ofCAN vehicle data 1904 a associated with HWID 19402 a, for example, to afleet manager including engine load data, speed data and RPM data ofvehicle 402 a.

At block 1808, subprocess 1800B includes receiving a plurality of firstcandidate data from the plurality of subprocess 1800A.

For example, remote server 404 receives first candidate data 2002 a,2002 b and 2002 c from monitoring devices 402 a, 402 b and 402 crespectively, as shown in FIG. 20A.

Next, at block 1809, subprocess 1800B includes identifyingmanufacturer-specific CAN data and determining a definition thereof forat least one vehicle type, e.g., identification data.

For instance, remote server 404 follows steps described in one or moresubprocesses including, subprocess 602 or 1600 for determining adefinition of manufacturer-specific CAN data, i.e., fuel rate, for atleast of one the vehicle types associated with vehicle type IDs 4574,6002, or 4628.

In this example, remote server 404 determines a definition ofmanufacturer-specific CAN data, i.e., fuel data, for a vehicle typeassociated with vehicle type IDs 4574. For instance, a definition formanufacturer-specific CAN data associated with a vehicle type associatedwith vehicle type ID 4574, includes CAN ID 0x500 and CAN payload bytes[4,5] as shown in data 2004 a.

Optionally, remote server 404 determines a definition ofmanufacturer-specific CAN data, i.e., fuel data, for multiple vehicletypes with associated vehicle type IDs 4574 and 6002 For instance, adefinition for manufacturer-specific CAN data associated with a vehicletype associated with vehicle type ID 4574, includes CAN ID 0x500 and CANpayload bytes [4,5] as shown in data 2004 a. A definition formanufacturer-specific CAN data associated with a vehicle type associatedwith vehicle type ID 6002, includes CAN ID 0x676 and CAN payload bytes[2,3] as shown in data 2004 a.

Further optionally, remote server 404 determines a definition ofmanufacturer-specific CAN data, i.e., fuel data, for multiple vehicletypes with associated vehicle type IDs 4574, 6002 and 4628. Forinstance, a definition for manufacturer-specific CAN data associatedwith a vehicle type associated with vehicle type ID 4574, includes CANID 0x500 and CAN payload bytes [4,5] as shown in data 2004 a. Adefinition for manufacturer-specific CAN data associated with a vehicletype associated with vehicle type ID 6002, includes CAN ID 0x676 and CANpayload bytes [2,3] as shown in data 2004 b. A definition formanufacturer-specific CAN data associated with a vehicle type associatedwith vehicle type ID 4628, includes CAN ID 0x01A and CAN payload bytes[0,1] as shown in data 2004 c.

Finally, in block 1810, subprocess 1800B includes providing instructiondata to a portion of the plurality of subprocesses 1800A for modifyingdefinition data to include a definition for manufacturer-specific CANdata associated with at least a first vehicle type.

For example, remote server 404 transmits to all monitoring devices 402first instruction data instructing monitoring devices to modifydefinition data 1902 to include a definition of manufacturer-specificCAN data 2005 a associated with the at least a vehicle type associatedwith vehicle type ID 5674.

Alternatively, remote server 404 transmits to a portion of monitoringdevices 402 corresponding to vehicle types associated with vehicle typeID 5674 first instruction data to modify definition data 1902 to includea definition of manufacturer-specific CAN data 2005 a associated withthe at least a vehicle type associated with vehicle type ID 5674.

Further alternatively, remote server 404 transmits first instructiondata to a portion of monitoring devices 402 corresponding to vehicletypes associated with vehicle type ID 5674 to modify definition data1902 to include a definition of manufacturer-specific CAN data 2005 aassociated with a vehicle type associated with vehicle type ID 5674.Then remote server 404 transmits second instruction data to anotherportion of monitoring devices 402 corresponding to vehicle typesassociated with vehicle type ID 6002 to modify definition data 1902 toinclude a definition of manufacturer-specific CAN data 2005 b associatedwith a vehicle type associated with vehicle type ID 6002.

Yet further alternatively, remote server generates second monitoringdevice instructions and transmits instruction data including the secondmonitoring device instructions. For example, second monitoring deviceinstructions may include instructions to perform a firmware upgrade anda corresponding firmware file. Second monitoring device instructionsfurther include definition data including a definition ofmanufacturer-specific CAN data.

According to an alternative embodiment, steps described in block 1803 ofsubprocess 1800A are not carried out unless a subprocess 1800A isassociated with a vehicle type for which a definition is not provided indefinition data.

For example, upon adding a new monitoring device 402 to telematicssystem 400, and detecting that definition data for manufacturer-specificCAN data (e.g., fuel data) is not included in definition data 1902, onlythen will the new monitoring device start to determine first candidatesas described in block 1803 of subprocess 1800A. In such instances, thenew monitoring device may be a monitoring device associated with a newvehicle type in telematics system 400. Alternatively, remote server 404may not have sufficient first candidate data to determine a definitionof manufacturer-specific data.

According to an embodiment, steps described in subprocess 1800A may beembodied in computer-executable instructions implemented as software,system software, firmware, middleware, embedded code, or any othersuitable type of computer code.

For example, steps described in subprocess 1800A may be performed onmonitoring device 402. For instance, monitoring device 402 may include afirst processing resource, e.g., processing resource 504, and a firstnon-transitory machine-readable storage medium, for example, stored indatastore 506 comprising first monitoring device instructions that whenexecuted cause the first processing resource to, collect vehicle CANdata based on definition data, transmit the vehicle CAN data to remoteserver 404, determine first candidate data indicative of firstcandidates for manufacturer-specific CAN data, transmit the firstcandidate data to remote server 404 and upon receiving second monitoringdevice instructions, storing the second monitoring device instructionsin the first non-transitory machine-readable storage medium, the secondmonitoring device instructions that when executed cause the processingresource to collect CAN payload data defined by definition data,definition data indicative of definitions of vehicle CAN data includinga definition of manufacturer-specific CAN data associated with the atleast a first vehicle type and transmit the vehicle CAN data.

According to an embodiment, steps described in subprocess 1800B may beembodied in computer-executable instructions implemented as software,system software, firmware, middleware, embedded code, or any othersuitable type of computer code.

For example, steps described in subprocess 1800B may be performed onremote server 404. For instance, remote server 404 may include a secondprocessing resource and a second non-transitory machine-readable storagemedium, for example, stored in a local datastore, comprisinginstructions that when executed cause the second processing resource to,receive from the plurality of monitoring devices a plurality of vehicleCAN data, process the plurality of vehicle CAN data for providing anindication of vehicle CAN data associated with at least a first HWID,receive a plurality of first candidate data, process the plurality ofthe first candidate data for determining a definition for themanufacturer-specific CAN data associated with the at least a firstvehicle type, generate second monitoring device instructions, andtransmit second monitoring device instructions to a portion of theplurality of monitoring devices associated with the at least a firstvehicle type.

Coefficient of Correlation

According to some embodiments, candidates for target data may beidentified based on a correlation coefficient between CAN payload dataand reference data, wherein the reference data is known to have a strongcorrelation with the manufacturer-specified CAN data (i.e., targetdata). As described hereinabove, target data may include one or morebytes of an undefined CAN message payload. Some embodiments may includedetermining a first correlation coefficient between one or more subsets,e.g., at least a first subset, of CAN payload data in any byteposition(s) [0] to [7] and the reference data. A high correlationcoefficient may indicate a subset of CAN payload data to be a candidatefor target data.

Subprocess 2100

Shown in FIG. 21 is a simplified flow diagram of a subprocess 2100 foridentifying one or more candidates for target data according to anembodiment. Subprocess 2100 includes identifying candidates based on ahigh correlation coefficient between reference data and CAN payloaddata. For instance, candidates may be identified by determining acoefficient of correlation between CAN payload data and fourth referencedata. In another instance, candidates may be identified by determining acoefficient of correlation between CAN payload data and a product of afourth reference data and a fifth reference data.

In a first example, target data may be in the form of fuel rate data, afourth reference data may be in the form of engine load data, and afifth reference data may be in a form of RPM data.

In the present example, candidates for target data, in the form of fuelrate data, may be identified by determining a correlation coefficientbetween CAN payload data and a product of fourth reference data in theform of engine load data and fifth reference data in the form of RPMdata.

For instance, airflow through a vehicle engine is proportional to EL*RPMi.e., engine load*revolutions per min. As fuel rate is proportional toairflow through a vehicle engine, fuel rate may also be proportional toa product of engine load and RPM. Correspondingly, there may a highcorrelation coefficient between fuel rate data and a product of engineload data and RPM data.

Beginning at block 2102, subprocess 2100 includes selecting a first CANID from a group of available CAN IDs. Some examples of available CAN IDsmay include unreserved CAN IDs in the SAE J1939 standard, the SAE J1962standard, and/or other vehicle bus standards.

In the present example, monitoring device 402 selects first CAN ID 0x400from a group of available CAN IDs including 0x001 to 0x7FF. However, anyavailable CAN ID from the group may be selected.

Next, at block 2104, subprocess 2100 includes collecting a plurality offourth reference data, a plurality of fifth reference data and aplurality of CAN payload data from a CAN bus and storing thereof in arolling buffer of size S.

In some instances, fourth reference data, fifth reference data and CANpayload data are collected at predefined intervals. Alternatively, theplurality of CAN payload data, fourth reference data and fifth referencedata are each collected at a time temporally proximate one another. Forexample, CAN payload data may be collected at the same time as, or at atime close to, the time fourth reference data, and at the same time, orat a time close to, the time fifth reference data is collected.

Shown in FIG. 22A is a conceptual diagram of a rolling buffer 2200 ofsize 12, i.e., S=12. In the present example, monitoring device 402collects fourth reference data in the form of engine load data 2202,fifth reference data in the form of RPM data 2204, and CAN payload data2207 corresponding to first CAN ID 0x400 from a CAN bus, such as CAN bus512, and stores this data in rolling buffer 2200. In this example,rolling buffer 2200 has a size of 12, however, a rolling buffer may beany size (i.e., have any number of slots). In some instances, RPM dataon a CAN bus is provided in units of 0.25 RPM/bit. In these instances,upon collecting RPM data on a CAN bus, a monitoring device may processthe collected RPM data, such as divide the collected RPM data by 4, andstore a result as RPM data in the rolling buffer. Alternatively, amonitoring device may convert RPM data at any time to reflect the actualRPM value.

Optionally, one or more of fourth reference data, fifth reference dataand CAN payload data may be stored in a separate rolling buffer of asame size, S.

For descriptive purposes, engine load data 2202, RPM data 2204, and CANpayload data 2207 are collected at a predefined interval of 1 second. Inpractise, however, this data may be collected at another predefinedinterval.

Rolling buffer 2200 comprises engine load data 2202-1 to 2202-12 inslots 1 to 12, respectively, RPM data 2204-1 to 2204-12 in slots 1 to12, respectively, and CAN payload data 2207-1 to 2207-12 in slots 1 to12, respectively, as shown.

FIG. 22B, is a conceptual diagram of CAN payload data 2207-1 to 2207-12presently stored in slots 1 to 12, respectively, of rolling buffer 2200.For instance, CAN payload data 2207-1 in slot 1 includes byte 2207-1-0in byte position [0], 2207-1-1 in byte position [1], 2207-1-2 in byteposition [2], and so forth. Similarly, CAN payload data 2207-12 in slot12 includes byte 2207-12-0 in byte position [0], 2207-12-1 in byteposition [1], 2207-12-2 in byte position [2], and so forth. Shown inFIG. 23A, shown are exemplary engine load values 2302 indicative ofengine load data 2202 and exemplary RPM values 2304 indicative of RPMdata 2204 presently stored in rolling buffer 2200.

Next, at block 2106, subprocess 2100 includes determining a firstcorrelation coefficient between each of the one or more subsets, e.g.,at least a first subset, of the CAN payload data and a product of fourthreference data and fifth reference data. Subprocess 2100 furtherincludes forming first correlation coefficient data indicative of thefirst correlation coefficients.

In the present example, monitoring device 402 processes engine load data2202 and RPM data 2204 to calculate a product thereof to form productdata 2210, shown in FIG. 22C. Exemplary values 2310 of product data2210, (i.e., EL*RPM) are shown in FIG. 23B.

Monitoring device 402 then determines a first correlation coefficientbetween one or more subsets, e.g., at least a first subset, of CANpayload data 2207 and product data 2210.

According to an embodiment, determining a first correlation coefficientbetween one or more subsets, e.g., at least a first subset, of the CANpayload data and a product of fourth reference data and fifth referencedata may be determined according to Pearson's correlation coefficient, astatistic that measures linear correlation between two variables X andY, and is defined as

$\begin{matrix}{{{r1} = {\frac{{{Co}{Var}}\left( {X,Y} \right)}{\sqrt{{Var}(X)}\sqrt{{Var}(Y)}} = \frac{{{Co}{Var}}\left( {X,Y} \right)}{\sigma_{x}*\sigma_{y}}}},} & {{Eq}.1}\end{matrix}$

CoVar(X,Y) is the covariance of X and Y,

σx, is the standard deviation of X and oy is the standard deviation ofY.

The covariance of X and Y is defined as:

$\begin{matrix}{{{{Co}{Var}\left( {X,Y} \right)} = \frac{\sum\limits_{i = 0}^{n}\left\lbrack {\left( {x_{i} - \overset{¯}{x}} \right)*\left( {y_{i} - \overset{¯}{y}} \right)} \right\rbrack}{N}},} & {{Eq}.2}\end{matrix}$wherein

xi represents an i-th sample of X and x represents a mean of samples ofX,

yi represents an i-th sample Y and y represents a mean of samples Y, and

N represents the number of samples of each of X and Y.

The standard deviation, ax, of X, is defined as,

$\begin{matrix}{{\sigma x} = {\sqrt{{Var}(X)} = \sqrt{\frac{\sum\limits_{i = 1}^{n}\left( {x_{i} - \overset{\_}{x}} \right)^{2}}{N}}}} & {{Eq}.3}\end{matrix}$

Var(X) is the variance of X and is defined as,

$\begin{matrix}{{{Var}(X)} = \frac{\sum\limits_{i = 1}^{n}\left( {x_{i} - \overset{¯}{x}} \right)^{2}}{N}} & {{Eq}.4}\end{matrix}$

The standard deviation, σy, of Y, is defined as,

$\begin{matrix}{{\sigma y} = {\sqrt{{Var}(Y)} = \sqrt{\frac{\sum\limits_{i = 1}^{n}\left( {y_{i} - \overset{\_}{y}} \right)^{2}}{N}}}} & {{Eq}.5}\end{matrix}$

Var(Y) is the variance of Y and is defined by:

$\begin{matrix}{{{Var}(Y)} = \frac{\sum\limits_{i = 1}^{n}\left( {y_{i} - \overset{¯}{y}} \right)^{2}}{N}} & {{Eq}.6}\end{matrix}$

Pearson's correlation coefficient may be applied to a sample ofvariables X and Y for determining a correlation coefficienttherebetween. For instance, a sample may comprise paired data {(x1,y1),. . . , (xn, yn)} including n pairs of samples.

In the present example, a first correlation coefficient, r1, between asubset of CAN payload data 2207 and product data 2210, (i.e., EL*RPM) isdetermined according to Pearson's correlation coefficient.

For instance, X represents product data, i.e., a product of engine loaddata and RPM data, and Y represents a subset of CAN payload data.

Monitoring device 402 may calculate r1 according to the steps describedbelow.

Var(X)

Firstly, monitoring device 402 may calculate

${{Var}(X)} = \frac{\sum\limits_{i = 1}^{n}\left( {x_{i} - \overset{¯}{x}} \right)^{2}}{N}$

wherein xi represents an i-th instance of product data 2210. Forexample, x1 corresponds to a first instance of product data 2210-1,having exemplary value 2310-1, 831312, as shown in FIG. 23B. Nrepresents the number of instances of product data 2210. In thisexample, buffer 2200 has 12 slots, thus N=12. Monitoring device 402calculates x, a mean of all instances of product data 2210 to bex=450107.

Monitoring device 402 then calculates (x_(i)−x)² for each of the 12instances of product data 2210 to form first data. Exemplary values 2308of first data are shown in FIG. 23C. For example, (x_(i)−x)² for a firstinstance of product data 2210-1, a value 2308-1 of first data iscalculated as (831312−450107)2=145317246942.27, as shown.

Next, a total sum of first data is determined as having a value of,

${{\sum\limits_{i = 1}^{n}\left( {x_{i} - \overset{¯}{x}} \right)^{2}} = {578915305762\text{.6}}},$and then the variance of product data 2210 is determined as,

$\begin{matrix}{{{Var}(X)} = {\frac{\sum\limits_{i = 1}^{n}\left( {x_{i} - \overset{¯}{x}} \right)^{2}}{N} = {\frac{57891530576{2.7}}{12} = {4824294214{6.9.}}}}} & \end{matrix}$Var(Y)

Secondly, monitoring device 402 may calculate Var(Y) for a subset of CANpayload data 2207.

A first exemplary subset of CAN payload data 2207 is shown in FIG. 22Bincluding a byte in a same byte position of CAN payload data 2207presently stored in each slot of rolling buffer 2200, such as subset2207-z-0 in byte position [0]. Exemplary values 2307-0 of subset2207-z-0 of CAN payload data 2207 are shown in FIG. 23D.

Monitoring device 402 calculates Var(Y) for subset 2207-z-0 of CANpayload data 2207,

${{Var}(Y)} = \frac{\sum\limits_{i = 1}^{n}\left( {y_{i} - \overset{¯}{y}} \right)^{2}}{N}$

wherein yi represents an i-th instance of a subset 2207-z-0 of CANpayload data 2207. For example, y1 corresponds to a first instance2207-1-0 of subset 2207-z-0 of CAN payload data 2207, having exemplaryvalue 2307-0-1, 45, as shown in FIG. 23D. N represents the number ofinstances of subset 2207-z-0 of CAN payload data 2207. In this example,buffer 2200 has 12 slots, thus N=12. Monitoring device 402 calculates y,a mean of all instances of subset 2207-z-0 of CAN payload data 2207 tobe y=22.32.

Monitoring device 402 then calculates (y_(i)−y)² for each of the 12instances of subset 2207-z-0 of CAN payload data 2207 to form seconddata. Exemplary values 2309 of second data are shown in FIG. 23E. Forexample, for first instance 2207-1-0 of subset 2207-z-0 of CAN payloaddata 2207 a value 2309-1 of second data is calculated as(45−22.32)2=514.53, as shown.

Next, a total sum of second data is determined as having a value of

$\frac{\sum\limits_{i = 1}^{n}{= \left( {y_{i} - \overset{¯}{y}} \right)^{2}}}{N} = {298{3.2}4}$and then the variance of subset 2207-z-0 of CAN payload data 2207 isdetermined as,

${{Var}(Y)} = {\frac{\sum\limits_{i = 1}^{n}\left( {y_{i} - \overset{¯}{y}} \right)^{2}}{N} = {\frac{2983.24}{12} = {24{8.6.}}}}$CoVar(X,Y)

Thirdly, monitoring device 402 may calculate for each instance of subset2207-z-0 of CAN payload data 2207 and product data 2206, (xi−x)*(yi−y)to form third data. Exemplary values 2312 of third data are shown inFIG. 23F.

For example, for a first instance of product data 2210-01 a value of(xi−x)=831312-450107=381205 and for a first instance of a subset2207-z-0 of CAN payload data 2207 a value of (yi−y)=45−22.32=22.68 isdetermined. Thus, a first value 2312-1 of third data is calculated as(xi−x)*(yi−y)=381205*22.68=8646999.9, as shown in FIG. 23F.

Monitoring device 402 then calculates

${\sum\limits_{i = 0}^{n}\left\lbrack {\left( {x_{i} - \overset{¯}{x}} \right)*\left( {y_{i} - \overset{¯}{y}} \right)} \right\rbrack} = {4091577{5.4}7}$and the covariance of X and Y,

${{{Co}{Var}}\left( {X,Y} \right)} = {\frac{\sum\limits_{i = 0}^{n}\left\lbrack {\left( {x_{i} - \overset{\_}{x}} \right)*\left( {y_{i} - \overset{¯}{y}} \right)} \right\rbrack}{N} = {\frac{40915775.47}{12} = {340964{7.9}5}}}$

Finally, monitoring device 402 determines r1, a first coefficient ofcorrelation between subset 2207-z-0 of CAN payload data 2207 and productdata 2210 as,

${r1} = {\frac{{CoVar}\left( {X,Y} \right)}{\sqrt{{Var}(X)}\sqrt{{Var}(Y)}} = {\frac{{CoVar}\left( {X,Y} \right)}{\sigma_{x}*\sigma_{y}} = {\frac{340964{7.9}5}{\sqrt{4824294214{6.9}*24{8.6}}} = {{.9}085}}}}$

Monitoring device 402 may form first correlation coefficient data 2400-0corresponding to a first correlation coefficient 2402 between subset2207-z-0 of CAN payload data 2207 and product data 2210, as shown inFIG. 24A

In this example, monitoring device 402 further calculates a plurality offirst correlation coefficients between each subset of a single byte ofCAN payload data in each byte position [1] to [7] and product data 2210,and forms first correlation coefficient data 2400 indicative thereof,such as first correlation coefficient data 2400-1 to 2400-7 shown inFIG. 24A.

Exemplary subsets of a single byte of CAN payload data in each byteposition [1] to [7] include bytes is positions [1], [2], [3], [4], [5],[6], and [7], corresponding to first correlation coefficient data2400_1, 24002, 24003, 2400_4, 2400_5, 2400_6, and 2400_7, respectively.

Additionally, and/or alternatively, monitoring device 402 may calculatea first coefficient of correlation between each subset of two bytes ofCAN payload data 2207 in ordered byte positions [1] to [7] and productdata 2210, and form first correlation coefficient data 2400-02 to2400-67 indicative thereof, as shown in FIG. 24A.

An exemplary subset of two bytes of CAN payload data in ordered bytepositions [1] to [7] include subset 2207-z-0,1 occupying byte positions[0,1]. Other exemplary subsets of two bytes of CAN payload data inordered byte positions [1] to [7] include bytes is positions, [1,2],[2,3], [3,4], [4,5], [5,6], and [6,7], corresponding to firstcorrelation coefficient data 2400_01, 2400_12, 2400_23, 2400_34,2400_45, 2400_56, and 2400_67, respectively.

Additionally, and/or alternatively, monitoring device 402 may calculatea first coefficient of correlation between each subset of two CANpayload data 2207 in ordered byte positions [1] to [7] in reverse order,and product data 2210, and form first correlation coefficient data2400_10 to 2400_76 as shown in FIG. 24A.

An exemplary subset of two bytes of CAN payload data in reverse orderedbyte positions [1] to [7] include subset [2207-z-1,0] occupying bytepositions [1,0], as shown in FIG. 22D. Other exemplary subsets of twobytes of CAN payload data in positions [1] to [7] in reverse orderincludes bytes in byte positions, [2,1], [3,2], [4,3], [5,4], [6,5], and[7,6], corresponding to first correlation coefficient data 2400_10,2400_21, 2400_32, 2400_43, 2400_54, 2400_65, and 2400_76, respectively.

Additionally, and/or alternatively, monitoring device 402 calculates afirst coefficient of correlation between other subsets of ordered bytesof CAN payload data 2207 and product data 2210 and forms firstcorrelation coefficient data. Exemplary subsets of ordered bytes includebytes in positions: [0,1,2], [1,2,3], [2,3,4], [3,4,5], [4,5,6],[5,6,7], among others.

Additionally, and/or alternatively, monitoring device 402 calculates afirst coefficient of correlation between other subsets of reverseordered bytes of CAN payload data 2307 product data 2306 and forms firstcorrelation coefficient data. Exemplary subsets of reverse ordered bytesinclude bytes in byte positions: [2,1,0], [3,2,1], [4,3,2], [5,4,3],[6,5,4], [7,6,5], among others.

Next, at block 2108, subprocess 2100 includes processing firstcorrelation coefficient data indicative of the plurality of firstcorrelation coefficients for determining whether any thereof meets aseventh criterion.

In the present example, monitoring device 402 processes firstcorrelation coefficient data 2400 for determining whether an instancethereof meets a seventh criterion, for example meets or exceeds a fourthpredefined threshold, such as, 0.90. A first correlation coefficientequal to or greater than 0.90 indicates there is a strong correlationbetween a corresponding subset of CAN payload data 2207 and product data2210.

Referring again to FIG. 24A, each of first correlation coefficients2402-0, 0.90, 2402-12, 0.91, and 2402-54, 0.92, corresponding to subsets[0], [0,1] and [5,4] of CAN payload data 2207, respectively, meets orexceeds 0.90. As such subprocess 2100 proceeds to block 2110. However,should no first correlation coefficient 2402 meet or exceed 0.90,process 2100 proceeds directly to block 2112.

At block 2110, subprocess 2100 includes forming first candidate databased on a first correlation coefficient meeting the seventh criterion.First candidate data indicating the one or more first byte positions ofthe CAN payload data occupied by the at least a first subset of the CANpayload data and the first CAN ID associated with the first correlationcoefficient meeting the seventh criterion.

For example, as mentioned hereinabove, each of first correlationcoefficients 2402-0, 0.90, 2402-12, 0.91, and 2402-54, 0.92,corresponding to subsets in byte positions [0], [0,1] and [5,4] of CANpayload data 2207, respectively, meets or exceeds 0.90.

As such, monitoring device 402 forms first candidate data 2408indicative thereof, as shown in FIG. 24B. For instance, first candidatedata 2408 a indicates a candidate of target data in byte position [0] ofan undefined CAN payload corresponding to CAN ID 0x400. First candidatedata 2408 b indicates a candidate of target data in byte positions [1,2]of an undefined CAN payload corresponding to CAN ID 0x400. Finally,first candidate data 2408 c indicates a candidate of target data in byteposition [5,4] of an undefined CAN payload corresponding to CAN ID0x400. Optionally, first candidate data 2408 includes data indicative ofa corresponding first correlation coefficient.

In some instances, monitoring device 402 may transmit first candidatedata 2408 to remote server 404 via communication network 406.

At block 2112, subprocess 2100 includes determining whether there isother CAN payload data corresponding to another first CAN ID of thegroup of available CAN IDs to be processed. If so, subprocess 2100returns to block 2102, otherwise, subprocess 2100 is complete.

For example, monitoring device 402 determines whether CAN payload datacorresponding to another first CAN ID in the group of available CAN IDscomprising 0x001 to 0x7FF, is still to be processed. If this is thecase, subprocess 2100 returns to block 2101 wherein another first CAN IDis selected, for instance, 0x689.

In some instances, CAN messages corresponding to a selected first CAN IDare not transmitted on the CAN bus. In such instances, subprocess 2100may timeout and proceed directly to block 2112.

Alternatively, subprocess 2100 includes identifying one or more firstcandidates for target data based on a high correlation coefficientbetween fourth reference data and CAN payload data, wherein the fourthreference data has at least a fourth correlation relationship with themanufacturer-specific CAN data.

For instance, at block 2104, subprocess 2100 includes collecting aplurality of fourth reference data and a plurality of CAN payload datafrom a CAN bus and storing thereof in a rolling buffer of size S. Atblock 2104, subprocess 2100 does not include collecting and storingfifth reference data. Then at block 2106, subprocess 2100 includesdetermining a first coefficient of correlation between one or moresubsets, e.g., at least a first subset, of the CAN payload data and afourth reference data.

For example, at block 2106, a first coefficient of correlation betweenone or more subsets, e.g., at least a first subset, of the CAN payloaddata and a fourth reference data may be determined according toPearson's correlation coefficient,

$\begin{matrix}{{{r1} = {\frac{{CoVar}\left( {X,Y} \right)}{\sqrt{{Var}(X)}\sqrt{{Var}(Y)}} = \frac{{CoVar}\left( {X,Y} \right)}{\sigma_{x}*\sigma_{y}}}},} & {{Eq}.1}\end{matrix}$

X represents fourth reference data, i.e., engine load data, and Yrepresents a subset of CAN payload data.

The example above describes target data, i.e., undefinedmanufacturer-specific CAN data, as fuel rate data, fourth data as engineload data, and fifth reference data as RPM data for illustrativepurposes only. However, target data, fourth reference data and fifthreference data may be any vehicle variable-related data. Specific andnon-limiting examples of target data include, odometer data and speeddata, e.g., speed data included in manufacturer-specific CAN data.

Target data, fourth reference data, fifth reference data and seventhcriterion in the examples described above are provided for explanationpurposes only. Similarly, other steps for calculating a firstcorrelation coefficient may be implemented. Embodiments are not intendedto be limited to the examples described herein.

Subprocess 2500

In some instances, a desired number of fourth reference data and CANpayload data samples to be collected for determining an accurate firstcorrelation coefficient is greater than allotted storage capacity of arolling buffer. For example, 60 samples of fourth reference data, fifthreference data and CAN payload data may be desired to be collected fordetermining a first correlation coefficient between CAN payload data anda product of fourth reference data and fifth reference data. However, arolling buffer may have been allotted storage capacity to store 12samples (i.e., has been allotted only 12 slots). A method fordetermining a first correlation coefficient between CAN payload data anda product of fourth reference data and fifth reference data when arolling buffer has insufficient storage capacity is described below.

Shown in FIG. 25 is a simplified flow diagram of a subprocess 2500 foridentifying one or more candidates for target data according to anembodiment. Subprocess 2500 includes identifying candidates based on ahigh correlation coefficient between CAN payload data and a product offourth reference data and fifth reference data. Subprocess 2500 mayinclude determining a first correlation coefficient by averaging aplurality of first correlation coefficients determined over a period oftime.

For example, candidates for target data, in the form of fuelconsumption, may be identified by determining a first coefficient ofcorrelation between CAN payload and a product of fourth reference datain the form of a product of engine load data and fifth reference data inthe form RPM data.

In the present example, 60 samples of engine load data, RPM data and CANpayload data are to be collected for determining a first correlationcoefficient between CAN payload data and a product of engine load dataand RPM data. However, in this example, rolling buffer 2200 ofmonitoring device 402, has a storage capacity allotment of only 12slots, (i.e., S=12) and cannot accommodate 60 samples simultaneously.Subprocess 2500 overcomes this limitation by averaging a plurality offirst correlation coefficients over a period of time.

The functionality of some blocks of subprocess 2500 to be describedbelow are the same and/or substantially similar to blocks of subprocess2100 and the previous description of the latter can be applied to theformer with the exceptions as described below.

At blocks 2102 and 2104, subprocess 2500 includes selecting a first CANID and collecting fourth reference data, fifth reference data and CANpayload data as described hereinabove with reference to subprocess 2100in FIG. 21 .

For example, monitoring device 402 collects engine load data 2202, RPMdata 2204 and CAN payload data 2207 corresponding to a first CAN ID0x400 and stores the data in rolling buffer 2200.

In some instances, RPM data on a CAN bus is provided in units of 0.25RPM/bit. In these instances, upon collecting RPM data on a CAN bus, amonitoring device may process the collected RPM data, such as divide thecollected RPM data by 4, and store a result as RPM data in the rollingbuffer. Alternatively, a monitoring device may convert RPM data at anytime to reflect the actual RPM value.

Next, at block 2506, subprocess 2500 determines a first correlationcoefficient between one or more subsets, e.g., at least a first subset,of CAN payload data and a product of fourth reference data and fifthreference data. Steps performed at block 2506 are the same as those atblock 2106 with one exception. Upon formation of first correlationcoefficient data, subprocess 2500 repeats the loop of blocks 2104 to2506 a predefined number, X, times, to form and store a plurality offirst correlation coefficients.

For example, monitoring device 402 forms first correlation coefficientdata 2600A based on engine load data 2202, RPM data 2204 and CAN payloaddata 2207 currently present in rolling buffer 2200. For instance, firstcorrelation coefficient data 2600A_0 corresponds to a first correlationcoefficient 0.86 between a subset of CAN payload data 2207 in byteposition [0] (i.e., CAN payload data 2207-z-0) and product data 2210.

Additionally, and/or alternatively, monitoring device 402 furthercalculates a plurality of first correlation coefficients between eachsubset of a single byte of CAN payload data in each byte position [1] to[7] and product data 2210, and forms first correlation coefficient data2600A indicative thereof, such as first correlation coefficient data2600A_1 to 2600A_7 shown in FIG. 26A. Exemplary subsets of a single byteof CAN payload data in each byte position [1] to [7] include bytes inpositions [1], [2], [3], [4], [5], [6], and [7], corresponding to firstcorrelation coefficient data 2600A_1 to 2600A_7, respectively.

Additionally, and/or alternatively, monitoring device 402 thencalculates a first coefficient of correlation between each subset of twobytes of CAN payload data 2207 in ordered byte positions [1] to [7] andproduct data 2210, and forms first correlation coefficient data 2600A_01to 2600A_67 indicative thereof, as shown in FIG. 26A. An exemplarysubset of two bytes of CAN payload data in ordered byte positions [1] to[7] include a subset occupying byte positions [0,1]. Other exemplarysubsets of two bytes of CAN payload data in ordered byte positions [1]to [7] include bytes in positions, [1,2], [2,3], [3,4], [4,5], [5,6],and [6,7], corresponding to first coefficient data 2600A_01 to 2600A_67,respectively.

Additionally, and/or alternatively, monitoring device 402 calculates afirst coefficient of correlation between each subset of two CAN payloaddata 2207 in ordered byte positions [1] to [7] in reverse order, andproduct data 2210, and forms first correlation coefficient data 2600A_10to 2600A_76 as shown in FIG. 26A. An exemplary subset of two bytes ofCAN payload data in reverse ordered byte positions [1] to [7] include asubset occupying byte positions [1,0]. Other exemplary subsets of twobytes of CAN payload data in positions [1] to [7] in reverse orderincludes bytes in byte positions, [2,1], [3,2], [4,3], [5,4], [6,5], and[7,6], corresponding to first coefficient data 2600A_10 to 2600A_76,respectively.

Monitoring device 402 then stores first correlation coefficient data2600A, for instance, in datastore 506.

Next, monitoring device 402 reiterates loop of blocks 2104 to 2506 X=4times. In this example, 60 samples of engine load data, RPM data and CANpayload data are to be collected for determining a first correlationcoefficient between CAN payload data and a product of engine load dataand RPM data. As rolling buffer 2200 has only 12 slots, monitoringdevice 402 iterates loop of blocks 2104 to 2506 5 times such that atotal of 60 samples are collected it total.

During each iteration, new engine load data, RPM data and CAN payloaddata are collected and stored in slots 1 to 12 of rolling buffer 2200,and first correlation coefficient data is formed based on engine loaddata, RPM data and CAN payload data present in buffer 2200. Forinstance, first correlation coefficient data 2600B, 2600C, 2600D and2600E, shown in FIGS. 26B, 26C, 26D and 26E, is formed at each of thefour reiterations of loop of blocks 2104 to 2506, respectively.

Monitoring device 402 then stores first correlation coefficient data2600B, 26000, 2600D and 2600E, for instance, in datastore 506.

At block 2507, subprocess 2500 includes averaging the plurality of firstcorrelation coefficients for determining a first correlation coefficientbetween CAN payload data and a product of fourth reference data andfifth reference data. Block 2507 is further described below withreference to FIGS. 26A, 26B, 26C, 26D, 26E and 26F.

For example, monitoring device 402 averages the plurality of firstcorrelation coefficients indicated by first correlation coefficient data2600A_0, 0.86, 2600B_0, 0.87, 2600C_0, 0.86, 2600D_0, 0.94, and 2600E_0,0.97, and forms first coefficient data 2600F_0, 0.90, indicativethereof.

Monitoring device 402 averages the remaining plurality of firstcorrelation coefficients indicated by first correlation coefficient data2600A, 2600B, 26000, 2600D and 2600E to form first correlationcoefficient data 2600F.

Next, at block 2508, subprocess 2500 includes processing each of theplurality of first correlation coefficients for determining whether anythereof meets a seventh criterion.

In the present example, monitoring device 402 processes firstcorrelation coefficient data 2600F for determining whether an instancethereof meets a seventh criterion. An exemplary seventh criterionincludes meeting or exceeding a fourth predefined threshold, such as,0.90. A first correlation coefficient greater than 0.90 indicates astrong correlation between a corresponding subset of CAN payload dataand a product of engine load and RPM.

Referring to FIG. 26F, each first correlation coefficient 2600F_0, 0.90,2600F_12, 0.91, and 2600F_54, 0.92, corresponding to subsets [0], [0,1]and [5,4] of CAN payload data, respectively, meets or exceeds 0.90. Assuch subprocess 2500 proceeds to block 2110. However, should none offirst correlation coefficients 2600F meet or exceed 0.90, process 2500proceeds directly to block 2112.

At block 2110, first candidate data is formed as described hereinabovein relation to subprocess 2100 of FIG. 21 . In some instances,monitoring device 402 may transmit first candidate data 2408 to remoteserver 404 via communication network 406.

At block 2112 subprocess 2500 includes determining whether there isother CAN payload data corresponding to another first CAN ID of thegroup of available CAN IDs to be processed as described hereinabove inrelation to subprocess 2100 of FIG. 21 . If there is no other CANpayload data to be processed subprocess 2500 is complete.

The example above describes target data, i.e., undefinedmanufacturer-specific CAN data, as fuel rate data, fourth data as engineload data, and fifth reference data as RPM data for explanation purposesonly. However, target data, fourth reference data and fifth referencedata may be any vehicle variable-related data. Specific and non-limitingexamples of target data include, odometer data and speed data, e.g.,speed data included in manufacturer-specific CAN data.

Target data, fourth reference data, and seventh criterion described inthe examples described above are provided for explanation purposes only.Similarly, other steps for calculating a first correlation coefficientmay be implemented. Embodiments are not intended to be limited to theexamples described herein.

Subprocess 2700

In some instances, a vehicle manufacturer may transmit engine load dataon a CAN bus corresponding to a manufacturer-specific CAN ID. In suchcases, false positive candidates for target data may be identified. Forexample, CAN payload data that includes engine load data may appear tobe fuel rate data because a high correlation coefficient between CANpayload data and a product of engine load data and RPM is determined.Methods for identifying one or more candidates for target data whileminimizing false positives are described below.

Shown in FIG. 27 is a simplified flow diagram of subprocess 2700 foridentifying one or more candidates for target data according to anembodiment.

The functionality of some blocks of subprocess 2700 to be describedbelow are the same and/or substantially similar to blocks of subprocess2100 and the previous description of the latter can be applied to theformer with the exceptions as described below.

At blocks 2102, 2104 and 2106 subprocess 2700 includes selecting a firstCAN ID, collecting fourth reference data, fifth reference data and CANpayload data, and determining a plurality of first correlationcoefficients, respectively, as described hereinabove with respect tosubprocess 2100 of FIG. 21

For example, monitoring device 402 collects engine load data 2202, RPMdata 2204 and CAN payload data 2207 corresponding to a first CAN ID0x400 and stores the data in rolling buffer 2200. Next, monitoringdevice 402 forms first correlation coefficient data 2400.

In some instances, RPM data on a CAN bus is provided in units of 0.25RPM/bit. In these instances, upon collecting RPM data on a CAN bus, amonitoring device may process the collected RPM data, such as divide thecollected RPM data by 4, and store a result as RPM data in the rollingbuffer. Alternatively, a monitoring device may convert RPM data at anytime to reflect the actual RPM value.

In some instances, RPM data on a CAN bus is provided in units of 0.25RPM/bit. In these instances, upon collecting RPM data on a CAN bus, amonitoring device may process the collected RPM data, such as divide thecollected RPM data by 4, and store a result as RPM data in the rollingbuffer. Alternatively, a monitoring device may convert RPM data at anytime to reflect the actual RPM value.

Next, at block 2707, subprocess 2700 includes determining a secondcorrelation coefficient between one or more subsets, e.g., at least afirst subset, of CAN payload data and the fourth reference dataincluding a same one or more subsets, e.g., at least a first subset, ofCAN payload data and the fourth reference data.

In this example, monitoring device 402 determines a second correlationcoefficient between the same plurality of subsets of CAN payload data2207 and engine load data 2202 processed at block 2106 in subprocess2100 as described herein above, for determining a second correlationcoefficient. For instance, if engine load data 2202 corresponding toexemplary engine load values 2302 are processed at block 2106 fordetermining a first correlation coefficient, the same are processed atblock 2707 for determining a second correlation coefficient.

For example, a second correlation coefficient, r2, between a subset ofCAN payload data 2207 and engine load data 2202 may be determinedaccording to Pearson's correlation coefficient, defined as

$\begin{matrix}{{r2} = {\frac{{CoVar}\left( {Z,Y} \right)}{\sqrt{{Var}(Z)}\sqrt{{Var}(Y)}} = {\frac{{CoVar}\left( {Z,Y} \right)}{\sigma_{z}*\sigma_{y}}.}}} & {{Eq}.7}\end{matrix}$

In this example, Z represents engine load data and Y represents a subsetof CAN payload data and σz, is the standard deviation of Z and σy is thestandard deviation of Y.

Monitoring device 402 may calculate r2 according to the steps describedbelow.

Var(Z)

Firstly, monitoring device 402 calculates

${{Var}(Z)} = \frac{\sum\limits_{i = 1}^{n}\left( {z_{i} - \overset{\_}{z}} \right)^{2}}{N}$

wherein zi represents an i-th instance of engine load data 2202. Forexample, z1 corresponds to a first instance of engine load data 2202-1,having exemplary value 2302-1, 110.4, as shown in FIG. 23A. N representsthe number of instances of engine load data 2202. In this example,buffer 2200 has 12 slots, thus N=12. Monitoring device 402 calculates z,a mean of all instances of engine load data 2202 to be z=74.92.

Monitoring device 402 then calculates (zi−z)² for each of the 12instances of engine load data 2202 to form fourth data. Exemplary values2802 of fourth data are shown in FIG. 28A. For example, (zi−z)² for afirst instance of engine load data 2202-1, a value 2802-1 of fourth datais calculated as (110.4−74.92)2=1259.07, as shown.

Next, the total sum of fourth data is determined as having a value of,

${{\sum\limits_{i = 1}^{n}\left( {z_{i} - \overset{¯}{z}} \right)^{2}} = {517{8.6}8}},$and then the variance of engine load data 2202 is determined as,

${{Var}(Z)} = {\frac{\sum\limits_{i = 1}^{n}\left( {z_{i} - \overset{¯}{z}} \right)^{2}}{N} = {\frac{517{8.6}8}{12} = {431}}}$

As discussed hereinabove, monitoring device 402 calculated Var(Y) forsubset of 2207-z-0 of CAN payload data 2207 to be,

${{Var}(Y)} = {\frac{\sum\limits_{i = 1}^{n}\left( {y_{i} - \overset{¯}{y}} \right)^{2}}{N} = {\frac{2983.24}{12} = {24{8.6.}}}}$CoVar(Z,Y)

Next, monitoring device 402 calculates for each instance of subset2207-z-0 of CAN payload data 2207 and engine load data 2202,(zi−z)*(yi−y) to form fifth data 2804. Exemplary values 2804 of fifthdata are shown in FIG. 28B.

For example, for a first instance of engine load data 2202-1 a value of,(zi−z)=110.4−74.92=35.48 and for a first instance of a subset 2207-z-0of CAN payload data 2207 a value of (yi−y)=45−22.32=22.68 is determined.Thus, a first value 2804-1 of fifth data is calculated as(zi−z)*(yi−y)=35.48*22.68=804.88 as shown in FIG. 28B.

Monitoring device 402 then calculates

${\sum\limits_{i = 0}^{n}\left\lbrack {\left( {z_{i} - \overset{¯}{z}} \right)*\left( {y_{i} - \overset{¯}{y}} \right)} \right\rbrack} = {326{2.8}0}$and the covariance of Z and Y,

${{{Co}{Var}}\left( {Z,Y} \right)} = {\frac{\sum\limits_{i = 0}^{n}\left\lbrack {\left( {z_{i} - \overset{¯}{z}} \right)*\left( {y_{i} - \overset{¯}{y}} \right)} \right\rbrack}{N} = {\frac{3262.8}{12} = {27{1.9}}}}$

Finally, monitoring device 402 determines r2, a second coefficient ofcorrelation between engine load data 2202 and a subset 2207-z-0 of CANpayload data 2207 as,

${r2} = {\frac{{Co}{Var}\left( {Z,Y} \right)}{\sqrt{{Var}(Z)}\sqrt{{Var}(Y)}} = {\frac{{Co}{Var}\left( {Z,Y} \right)}{\sigma_{z}*\sigma_{y}} = {\frac{271.9}{\sqrt{\left( {431*248.6} \right)}} = {{.8}3}}}}$

Monitoring device 402 may form second correlation coefficient data2806-0 corresponding to a second correlation coefficient 2806 betweensubset 2207-z-0 of CAN payload data 2207 and product data 2210, as shownin FIG. 28C.

In this example, monitoring device 402 further calculates a plurality ofsecond correlation coefficients between each subset of a single byte ofCAN payload data in each byte position [1] to [7] and engine load data2202, and forms second correlation coefficient data 2806 indicativethereof, such as second correlation coefficient data 2806-1 to 2806-7,as shown in FIG. 28C.

Exemplary subsets of a single byte of CAN payload data in each byteposition [1] to [7] include bytes is positions [1], [2], [3], [4], [5],[6], and [7], corresponding to second correlation coefficient data2806_1, 2806_2, 2806_3, 2806_4, 2806_5, 2806_6, and 2806_7,respectively.

Additionally, and/or alternatively, monitoring device 402 calculates asecond coefficient of correlation between each subset of two bytes ofCAN payload data 2207 in ordered byte positions [1] to [7] and engineload data 2302, and form further second correlation coefficient data2806 indicative thereof, as shown in FIG. 28 .

An exemplary subset of two bytes of CAN payload data in ordered bytepositions [1] to [7] include subset 2207-z-0,1 occupying byte positions[0,1]. Other exemplary subsets of two bytes of CAN payload data inordered byte positions [1] to [7] include bytes is positions, [1,2],[2,3], [3,4], [4,5], [5,6], and [6,7], corresponding to secondcorrelation coefficient data 2806_01, 2806_12, 2806_23, 2806_34,2806_45, 2806_56, and 2806_67, respectively.

Additionally, and/or alternatively, monitoring device 402 may calculatea second coefficient of correlation between each subset of two CANpayload data 2207 in ordered byte positions [1] to [7] in reverse order,engine load data 2202, and form second correlation coefficient data2806_10 to 2800_76, as shown in FIG. 28C.

An exemplary subset of two bytes of CAN payload data in reverse orderedbyte positions [1] to [7] include subset [2207-z-1,0] occupying bytepositions [1,0], as shown in FIG. 22D. Other exemplary subsets of twobytes of CAN payload data in positions [1] to [7] in reverse orderincludes bytes in byte positions, [2,1], [3,2], [4,3], [5,4], [6,5], and[7,6], corresponding to second correlation coefficient data 2806_10,2806_21, 2806_32, 2806_43, 2806_54, 2806_65, and 2806_76, respectively.

Additionally, and/or alternatively, monitoring device 402 calculates asecond coefficient of correlation between other subsets of ordered bytesof CAN payload data 2207 and engine load data 2202 and forms secondcorrelation coefficient data. Exemplary subsets of ordered bytes includebytes in positions: [0,1,2], [1,2,3], [2,3,4], [3,4,5], [4,5,6],[5,6,7], among others.

Additionally, and/or alternatively, monitoring device 402 calculates asecond coefficient of correlation between other subsets of reverseordered bytes of CAN payload data 2207 engine load data 2202 and formssecond correlation coefficient data. Exemplary subsets of reverseordered bytes include bytes in byte positions: [2,1,0], [3,2,1],[4,3,2], [5,4,3], [6,5,4], [7,6,5], among others.

Next, at block 2709, subprocess 2700 includes processing each of theplurality of first correlation coefficients for determining whether anythereof meets a seventh criterion and each of the plurality ofassociated second correlation coefficients for determining whether anythereof meets an eighth criterion.

In the present example, monitoring device 402 processes firstcorrelation coefficient data 2400 for determining whether an instancethereof meets a seventh criterion. Exemplary seventh criterion includesmeeting or exceeding a fourth predefined threshold, such as, 0.90. Afirst correlation coefficient the same or greater than 0.90 indicates astrong correlation between a corresponding subset of CAN payload data2207 and product data 2206.

Referring again to FIG. 24A, each of first correlation coefficients2400-0, 0.90, 2400-12, 0.91, and 2400-54, 0.92, corresponding to subsets[0], [0,1] and [5,4] of CAN payload data 2207, respectively meets orexceeds 0.90. Should none of first correlation coefficients 2400 meet orexceed 0.90, process 2700 proceeds to directly block 2712.

Next monitoring device 402 processes second correlation coefficient data2806 associated with each first correlation coefficient data 2400 thatmeets the fourth predefined threshold, for determining whether aninstance thereof meets an eighth criterion. Exemplary eighth criterionincludes not exceeding a fifth predefined threshold, such as, 0.95. Forinstance, second correlation coefficient data 2806 associated with eachof first correlation coefficients 2400_0, 2400_12, and 2400_54, isprocessed to determine whether it does not exceed a fifth predefinedthreshold, such as 0.95. In this example, second correlationcoefficients 2806_0, 0.44, 2806_12, 0.99, and 2806_54, 0.98, correspondto first correlation coefficients 24000, 2400_12, and 2400_54,respectively. Second correlation coefficient 2806_0, 0.44, does notexceeds the fifth predefined threshold 0.95 and thus meets the eighthcriterion. As such, process 2700 proceeds to block 2710. However, shouldall second correlation coefficients 2806 exceed 0.95, process 2700proceeds directly block 2712. At block 2710, subprocess 2700 includesforming first candidate data based on a first correlation coefficientmeeting the seventh criterion and a corresponding second correlationcoefficient meeting an eighth criterion.

For example, as mentioned hereinabove, first correlation coefficients2400-0 corresponding to subset [0] of CAN payload data 2207 meets theseventh criterion and corresponding second correlation coefficient2806_0 meets the eighth criterion.

As such, monitoring device 402 forms first candidate data 2810 shown inFIG. 28D indicating a candidate of the target data in byte position [0]of an undefined CAN payload corresponding to CAN ID 0x400. Optionally,candidate data 2810 includes data indicative of a corresponding firstcorrelation coefficient.

In some instances, monitoring device 402 may transmit first candidatedata 2810 to remote server 404 via communication network 406.

At block 2712, subprocess 2700 includes determining whether there isother CAN payload data corresponding to another first CAN ID of thegroup of available CAN IDs to be processed. If so, subprocess 2700returns to block 2102, otherwise, subprocess 2700 is complete.

For example, monitoring device 402 determines whether CAN payload datacorresponding to another first CAN ID in the group of available CAN IDscomprising 0x001 to 0x7FF, is still to be processed. If this is thecase, subprocess 2700 returns to block 2102 wherein another first CAN IDis selected, for instance, 0x689.

In some instances, CAN messages corresponding to a selected first CAN IDare not transmitted on the CAN bus. In such instances, subprocess 2700may timeout and proceed directly to block 2712.

The example above describes target data, i.e., undefinedmanufacturer-specific CAN data, as fuel rate data, fourth data as engineload data, and fifth reference data as RPM data for illustrativepurposes only. However, target data, fourth reference data and fifthreference data may be any vehicle variable-related data. Specific andnon-limiting examples of target data include, odometer data and speeddata, e.g., speed data included in manufacturer-specific CAN data.

Target data, fourth reference data, fifth reference data, seventhcriterion, and eighth criterion, described in the examples describedabove are provided for explanation purposes only. Similarly, other stepsfor calculating a first and second correlation coefficient may beimplemented. Embodiments are not intended to be limited to the examplesdescribed herein.

Subprocess 2900

In some instances, a vehicle manufacturer may transmit engine load dataon a CAN bus corresponding to a manufacturer-specific CAN ID. In suchcases, false positive candidates for target data may be identified. Insome other instances, a desired number of fourth reference data and CANpayload data samples to be collected for determining an accurate firstcorrelation coefficient is greater than allotted storage capacity of arolling buffer. For example, 60 samples of fourth reference data, fifthreference data and CAN payload data may be desired to be collected fordetermining a first correlation coefficient between CAN payload data anda product of fourth reference data and fifth reference data. However, arolling buffer may have been allotted storage capacity to store 12samples (i.e., has been allotted only 12 slots). A method fordetermining a first correlation coefficient between CAN payload data anda product of fourth reference data and fifth reference data forminimizing false positives and when a rolling buffer has insufficientstorage capacity is described below.

Shown in FIG. 29 is a simplified flow diagram of another subprocess 2900for identifying one or more candidates for target data based on a highcorrelation coefficient between a product of fourth reference data andfifth reference data, and CAN payload data according to an embodiment.

In a first example, target data may be in the form of fuel rate data, afourth reference data may be in the form of engine load data, and afifth reference data may be in a form of RPM data.

In the present example, candidates for target data, in the form of fuelrate data, may be identified by determining a correlation coefficientbetween CAN payload data and a product of fourth reference data in theform of engine load data and fifth reference data in the form of RPMdata.

The functionality of some blocks of subprocess 2900 to be describedbelow are the same and/or substantially similar to blocks of subprocess2100 and/or blocks of subprocess 2700 and the previous description ofthe latter can be applied to the former with the exceptions as describedbelow.

At blocks 2102 and 2104, subprocess 2900 includes selecting a first CANID and collecting fourth reference data and CAN payload data asdescribed hereinabove with reference to subprocess 2100 in FIG. 21 .

For example, monitoring device 402 collects engine load data 2302, RPMdata 2304 and CAN payload data 2307 corresponding to a first CAN ID0x400 and stores the data in rolling buffer 2200.

In some instances, RPM data on a CAN bus is provided in units of 0.25RPM/bit. In these instances, upon collecting RPM data on a CAN bus, amonitoring device may process the collected RPM data, such as divide thecollected RPM data by 4, and store a result as RPM data in the rollingbuffer. Alternatively, a monitoring device may convert RPM data at anytime to reflect the actual RPM value.

Next at block, 2106, subprocess 2900 includes determining a firstcorrelation coefficient between one or more subsets, e.g., at least afirst subset, e.g., at least a first subset, of the CAN payload data andthe fourth reference data.

For example, monitoring device 402 determines a first correlationcoefficient between one or more subsets, e.g., at least a first subset,e.g., at least a first subset, of the CAN payload data 2207 and aproduct data 2206 and forms first correlation coefficient data 2600A inFIG. 24A.

Next, at block 2907, subprocess 2900 includes determining a secondcorrelation coefficient between one or more subsets, e.g., at least afirst subset, e.g., at least a first subset, of the CAN payload data andthe fourth reference data.

Steps performed at block 2907 are the same as those at block 2707 withthe following differences: Upon formation of second correlationcoefficient data, subprocess 2900 repeats the loop of blocks 2104 to2907 a predefined number, X, times, to form and store a plurality offirst correlation coefficients and a plurality of second correlationcoefficients.

For example, monitoring device 402 determines a second correlationcoefficient between one or more subsets, e.g., at least a first subset,of the CAN payload data 2207 and engine load data 2202 and forms secondcorrelation coefficient data 3000_A, as shown in FIG. 30A.

Next, monitoring device 402 reiterates loops 2104 to 2907 four times,(i.e., X=4). During each iteration, new engine load data, RPM data andCAN payload data is collected, and first correlation coefficient data isformed based on engine load data, RPM data and CAN payload data presentin buffer 2200. For instance, first correlation coefficient data 2600_A,2600_B, 2600_C, 2600_D and 2600_E is formed at each of the 5 totaliterations of loop of blocks 2104 to 2907, respectively.

Furthermore, during each iteration, second correlation coefficient datais formed based on engine load data and CAN payload data present inbuffer 2200. For instance, second correlation coefficient data 3000_B,3000_C, 3000_D and 3000_E is formed at each of the four reiterations ofloop of blocks 2104 to 2907, respectively, as shown in FIGS. 30B, 30C,30D, and 30E.

Monitoring device 402 stores first correlation coefficient data 2600_A,2600_B, 2600_C, 2600_D and 2600_E, and second correlation coefficientdata 3000_A, 3000_B, 3000_C, 3000_D and 3000_E, for instance, indatastore 506.

Upon reiterating loops 2104 to 2907 four times, subprocess 2900 proceedsto block 2908.

At block 2908, subprocess 2900 includes averaging the plurality of firstcorrelation coefficients and the plurality of second correlationcoefficients.

For example, monitoring device 402 averages the plurality of firstcorrelation coefficients indicated by first correlation coefficient data2600A_0, 0.86, 2600B_0, 0.87, 2600C_0, 0.86, 2600D_0, 0.94, and 2600E_0,0.97, and forms first coefficient data 2600F_0, 0.90. Next, monitoringdevice 402 averages the plurality of second correlation coefficientsindicated by second correlation coefficient data 3000A_0, 0.41, 3000B_0,0.42, 3000C_0, 0.50, 3000D_0, 0.50, and 3000E_0, 0.42, and forms secondcoefficient data 3000F_0, 0.45 as shown in FIG. 30F.

Monitoring device 402 averages the remaining plurality of firstcorrelation coefficients indicated by first correlation coefficient data2600_A, 2600_B, 2600_C, 2600_D and 2600_E to form first correlationcoefficient data 2600_F and second correlation coefficient data 3000_B,3000_C, 3000_D and 3000_E to form second correlation coefficient data3000_F.

Next, at block 2709, subprocess 2900 includes processing each of theplurality of first correlation coefficients for determining whether anythereof meets a seventh criterion and each of the plurality ofassociated second correlation coefficients for determining whether anythereof meets an eighth criterion.

For instance, a seventh criterion may include meeting or exceeding afourth predefined threshold, such as, 0.90 and an eighth criterion mayinclude not exceeding a fifth predefined threshold, such as, 0.95

In the present example, monitoring device 402 determines each of firstcorrelation coefficients 2600F_0, 0.90, 2600F_12, 0.91, and 2600F_54,0.92, corresponding to subsets [0], [0,1] and [5,4] of CAN payload data,respectively, meets or exceeds 0.90.

Next, monitoring device 402 processes second correlation coefficientdata 3000_F associated with each of first correlation coefficients2600F_0, 2600F_12, and 2600F_54, to determine whether it does not exceeda fifth predefined threshold, such as 0.95. In this example, secondcorrelation coefficients 3000F_0, 0.44, 3000F_12, 0.99, and 3000F_54,0.99, correspond to first correlation coefficients 2400_0, 2400_12, and2400_54, respectively. Second correlation coefficient 3000F_0, 0.44,does not exceed the fifth predefined threshold 0.95 and thus meets theeighth criterion. As such, process 2900 proceeds to block 2710. However,should all second correlation coefficients 3000F exceed 0.95, process2900 proceeds to directly block 2712.

At block 2710, subprocess 2900 includes forming first candidate databased on a first correlation coefficient meeting the seventh criterionand a corresponding second correlation coefficient meeting the eighthcriterion, as described herein above with respect to subprocess 2700 inFIG. 27 .

As such, monitoring device 402 forms first candidate data 2810 shown inFIG. 28D indicating a candidate of the target data in byte position [0]of an undefined CAN payload corresponding to CAN ID 0x400.

Optionally, first candidate data 2810 includes data indicative of acorresponding first correlation coefficient. In such instances, forexample, at block 1608 of subprocess 1600, subprocess 1600 may furtherinclude processing data indicative of a corresponding first correlationcoefficient for determining which of the first candidates indicatedthereby is likely to indicate target data associated with the firstvehicle type.

In some instances, monitoring device 402 may transmit first candidatedata 2810 to remote server 404 via communication network 406.

At block 2712, subprocess 2900 includes determining whether there isother CAN payload data corresponding to another first CAN ID of thegroup of available CAN IDs to be processed as described hereinabove withrespect to subprocess 2700 in FIG. 27 .

The example above describes target data, i.e., undefinedmanufacturer-specific CAN data, as fuel rate data, fourth data as engineload data, and fifth reference data as RPM data for illustrativepurposes only. However, target data, fourth reference data and fifthreference data may be any vehicle variable-related data. Specific andnon-limiting examples of target data include, odometer data and speeddata, e.g., speed data included in manufacturer-specific CAN data.

Target data, fourth reference data, fifth reference data, seventhcriterion, and eighth criterion, described in the examples describedabove are provided for explanation purposes only. Similarly, other stepsfor calculating a first and second correlation coefficient may beimplemented. Embodiments are not intended to be limited to the examplesdescribed herein.

In some instances, a manufacturer may transmit manufacturer-specificaccumulated fuel consumption data on a CAN bus instead of fuel ratedata. Accumulated fuel consumption data represents the total fuelconsumed by a vehicle from initial operation to the time of transmissionof the accumulated fuel consumption data.

According to an embodiment, there is a method for converting CAN payloaddata carrying accumulated fuel consumption data into fuel rate data. Forinstance, the method includes collecting a plurality of fourth referencedata, a plurality of fifth reference data and a plurality of CAN payloaddata from a CAN bus. Next, the plurality of CAN payload data isprocessed prior to storing that data in a rolling buffer of size S.

For instance, the method includes processing present CAN payload data,an immediately previously received CAN payload data, and a time dataindicating a time interval between receiving the present CAN payloaddata and the immediately previously received CAN payload data fordetermining a rate of change of CAN payload data over time, i.e., fuelrate data. The fuel rate data many be stored as CAN payload data in theroller buffer simultaneously with the present fourth reference data andfifth reference data.

For example, shown in FIG. 31A is a conceptual diagram of data 3100,including CAN payload data 3106, fourth reference data 3102, and fifthreference data 3104 received by monitoring device 402 at predefinedintervals, for example, 1 second intervals. Time data is indicative of 1second. Data 3100 in FIG. 31A is presented in a time ordered sequence.For example, monitoring device 402 initially receives data 3100-0, asecond later it receives data 3100-1, a second after that it receivesdata 3100-2, and so on.

FIG. 31B shows a conceptual diagram of a rolling buffer, rolling buffer3200, having a size of 12, i.e., 12 slots.

Upon receiving data 3100-0, including CAN payload data 3106-0, fourthreference data 3102-0, and fifth reference data 3104-0, monitoringdevice 402 saves a copy of present CAN payload data 3106-0, for futureuse.

Next, monitoring device receives data 3100-1, including CAN payload data3106-1, fourth reference data 3102-1, and fifth reference data 3104-1and stores fourth reference data 3102-1 and fifth reference data 3106-1in slot 1 of rolling buffer 3200 as shown.

Monitoring device 402 processes immediately previously received CANpayload data 3106, present CAN payload data 3106-1 and time dataindicating 1 second, for determining a CAN payload data representingfuel rate data.

For example, CAN payload data 3106-0 represents an accumulated fuelconsumption of 2000 L, and CAN payload data 3106-1 and representsaccumulated fuel consumption of 2000.01 L. CAN payload data 3106-0 andCAN payload data 3106-1 were collected 1 s apart. Monitoring device 402determines a fuel rate of (2000.01 L−2000 L)/1 s=0.01 L/s. As such,monitoring device 402 stores CAN payload data 3108-1 representing 0.01L/s in slot 1 of rolling buffer 3200.

Monitoring device 402 maintains a copy of the present CAN payload data3106-1 for determining a fuel rate for the vehicle based thereon and thenext immediately received CAN payload data 3106-2.

Monitoring device 402 repeats the steps described above until all 12slots of the rolling buffer are filled.

For descriptive purposes, an immediately previously received CAN payloaddata and present CAN payload data is processed for determining fuel ratedata. Alternatively, one or more bytes of CAN payload data may beprocessed for determining fuel rate data.

For example, a byte in byte position [0] of a present CAN payload datarepresents 36,024.56 L of accumulated fuel consumption and a byte inbyte position [0] of an immediately previously received CAN payload datarepresents 36,024.52 L accumulated fuel consumption. Monitoring device402 determines a fuel rate of (36,024.56 L−36,024.52 L)/1 s=0.04 L/s. Inthis example, fuel rate data indicative of the fuel rate is stored inbyte position [0] of CAN payload data in a same slot of a rolling bufferas present fourth reference data and fifth reference data.

Monitoring device 402 may proceed to process one or more bytes in bytepositions [1] to [7] as described herein above.

Included in the discussion above are a series of flow charts showing thesteps and acts of various processes. The processing and decision blocksof the flow charts above represent steps and acts that may be includedin algorithms that carry out these various processes. Algorithms derivedfrom these processes may be implemented as software integrated with anddirecting the operation of one or more processors, may be implemented asfunctionally-equivalent circuits such as a Digital Signal Processing(DSP) circuit, a Field Programmable Gate Array (FPGA), anApplication-Specific Integrated Circuit (ASIC), or may be implemented inany other suitable manner. It should be appreciated that the flow chartsincluded herein do not depict the syntax or operation of any circuit orof any programming language or type of programming language. Rather, theflow charts illustrate the functional information one skilled in the artmay use to fabricate circuits or to implement computer softwarealgorithms to perform the processing of an apparatus carrying out thetypes of techniques described herein. It should also be appreciatedthat, unless otherwise indicated herein, the sequence of steps and/oracts described in each flow chart is merely illustrative of thealgorithms that may be implemented and can be varied in implementationsand embodiments of the principles described herein.

Accordingly, in some embodiments, the techniques described herein may beembodied in computer-executable instructions implemented as software,including as application software, system software, firmware,middleware, embedded code, or any other suitable type of computer code.Such computer-executable instructions may be written using any ofseveral suitable programming languages and/or programming or scriptingtools and may be compiled as executable machine language code orintermediate code that is executed on a framework or virtual machine.

Computer-executable instructions implementing the techniques describedherein may, in some embodiments, be encoded on one or morecomputer-readable media to provide functionality to the media.Computer-readable media include magnetic media such as a hard diskdrive, optical media such as a Compact Disk (CD) or a Digital VersatileDisk (DVD), Blu-Ray disk, a persistent or non-persistent solid-statememory (e.g., Flash memory, Magnetic RAM, etc.), or any other suitablestorage media. As used herein, “computer-readable media” (also called“computer-readable storage media”) refers to tangible storage media.Tangible storage media are non-transitory and have at least onephysical, structural component. In a “computer-readable medium,” as usedherein, at least one physical, structural component has at least onephysical property that may be altered in some way during a process ofcreating the medium with embedded information, a process of recordinginformation thereon, or any other process of encoding the medium withinformation. For example, a magnetization state of a portion of aphysical structure of a computer-readable medium may be altered during arecording process.

Embodiments have been described where the techniques are implemented incircuitry and/or computer-executable instructions. It should beappreciated that some embodiments may be in the form of a method orprocess, of which at least one example has been provided. The actsperformed as part of the method or process may be ordered in anysuitable way. Accordingly, embodiments may be constructed in which actsare performed in an order different than illustrated, which may includeperforming some acts simultaneously, even though shown as sequentialacts in illustrative embodiments. Various aspects of the embodimentsdescribed above may be used alone, in combination, or in a variety ofarrangements not specifically discussed in the embodiments described inthe foregoing and is therefore not limited in its application to thedetails and arrangement of components set forth in the foregoingdescription or illustrated in the drawings. For example, aspectsdescribed in one embodiment may be combined in any manner with aspectsdescribed in other embodiments.

It should be understood that aspects are described herein with referenceto certain illustrative embodiments. The illustrative embodimentsdescribed herein are not necessarily intended to show all aspects, butrather are used to describe a few illustrative embodiments. Thus,aspects described herein are not intended to be construed narrowly inview of the illustrative embodiments. In addition, it should beunderstood that certain features disclosed herein might be used alone orin any suitable combination with other features.

Technical Effects

Embodiments described herein provide one or more technical effects andimprovements to a telematics system, fleet management system andunderlying technology components. For example, an ability to identifymanufacturer-specific controller-area network data not defined invehicle bus standards, unique to a vehicle type, and generallyobfuscated from non-OEM parties, e.g., 3^(rd) parties, vehiclemonitoring devices for enabling remote identification ofmanufacturer-specific CAN data; spontaneous remote identification ofmanufacturer-specific CAN data for a new vehicle type added to atelematics system, including new vehicle types added to the vehiclemarket; a telematics system enabling parallel remote identification ofmanufacturer-specific CAN data for hundreds, thousands, or tens ofthousands of vehicles and vehicle types; leveraging remote communicationwith a large number of vehicles monitoring devices for enabling parallelremote identification of manufacturer-specific CAN data for hundreds,thousands, or tens of thousands of vehicles and vehicle types; oncemanufacturer-specific CAN data for a vehicle type is identified,automatic collection thereof, automatic collection and transmissionthereof to a fleet manager, and automatic reconfiguration of monitoringdevices for collection and transmission of newly identifiedmanufacturer-specific CAN data.

What is claimed is:
 1. A telematics system for identifyingmanufacturer-specific controller area network (CAN) data comprising: aplurality of monitoring devices, each thereof configured, for aplurality of first CAN IDs, for collecting CAN payload datacorresponding to the first CAN ID; collecting first reference datacorresponding to a second CAN ID having at least a first correlationrelationship with the manufacturer-specific CAN data; storing the firstreference data and the CAN payload data in a rolling buffer; followingreceipt of new first reference data and new CAN payload data,determining whether the first reference data present in the rollingbuffer meets a first criterion; in response to determining the firstreference data present in the rolling buffer meeting the firstcriterion, determining whether one or more first subsets of the CANpayload data present in the rolling buffer meets a second criterion,each of the one or more first subsets occupying a first byte position ineach slot of the rolling buffer; dependent on first reference datameeting the first criterion exceeding a first counting threshold, foreach of the one or more first subsets meeting the second criterionexceeding a second counting threshold, forming first position dataindicative of the first byte position in each slot of the rolling bufferoccupied thereby; forming first candidate data indicative of a firstcandidate of the manufacturer-specific CAN data corresponding to thefirst position data and the first CAN ID; a remote server in wirelesscommunication with each of the plurality of monitoring devices, theremote server configured for, selecting a subset of a plurality of thefirst candidate data corresponding to the first vehicle type to formsecond candidate data; selecting a second candidate from the secondcandidate data; and generating identification data corresponding to theidentity of the manufacturer-specific CAN data for the first vehicletype, the identification data indicative of a manufacturer-specific CANdata byte position and corresponding manufacturer-specific CAN data CANID associated with the second candidate data.
 2. The telematics systemof claim 1 wherein the first byte position includes a plurality of bytepositions.
 3. The telematics system of claim 1 wherein the firstcriterion and the second criterion are indicative of the at least firstcorrelation relationship.
 4. The telematics system of claim 1 whereindetermining whether the first reference data present in the rollingbuffer meets a first criterion comprises determining whether the firstreference data in each slot in the rolling buffer exceeds an immediatelypreviously received first reference data by at least a first predefinedthreshold.
 5. The telematics system of claim 1 wherein determiningwhether the first reference data present in the rolling buffer meets afirst criterion comprises determining whether a value represented by thefirst reference data in each slot in the rolling buffer exceeds a valuerepresented by an immediately previously received first reference databy at least a first predefined threshold.
 6. The telematics system ofclaim 1 wherein determining one or more first subsets of the CAN payloaddata meets a second criterion comprises determining for each subsetthereof, whether a difference between each consecutive pair of bytes inthe first byte position of the rolling buffer exceeds a secondpredefined threshold.
 7. The telematics system of claim 1 whereincollecting first reference data having at least a first correlationrelationship with the manufacturer-specific CAN data comprisescollecting first reference data having a first correlation relationshipwith the manufacturer-specific CAN data and collecting first referencedata having a second correlation relationship with themanufacturer-specific CAN data.
 8. The telematics system of claim 7wherein collecting first reference data having a second correlationrelationship with the manufacturer-specific CAN data comprisescollecting first reference data and second reference data having asecond correlation relationship with the manufacturer-specific CAN data.9. The telematics system of claim 1 wherein the plurality of monitoringdevices further configured for upon receipt of the new first referencedata and the new CAN payload data, determining whether the firstreference data present in the rolling buffer meets a third criterion; inresponse to determining the first reference data present in the rollingbuffer meeting the third criterion, determining whether one or moresecond subsets of the CAN payload data present in the rolling buffermeets a fourth criterion, each of the one or more second subsetsoccupying a second byte position in each slot of the rolling buffer;dependent on the first reference data meeting a third criterionexceeding a third counting threshold, for each of the one or more secondsubsets meeting the fourth criterion exceeding a fourth countingthreshold, forming second position data indicative of the second byteposition in each slot of the rolling buffer occupied thereby; andwherein forming first candidate data indicative of the first positiondata and the first CAN ID comprises forming first candidate dependent onthe first byte position of the first position data and the second byteposition of the second position data being same, and the first CAN ID.10. The telematics system of claim 9 wherein the third criterion and thefourth criterion are indicative of the second correlation relationship.11. The telematics system of claim 10 wherein determining whether one ormore second subsets of the CAN payload data present in the rollingbuffer meets a fourth criterion comprises determining whether therelative difference in value of the one or more second subsets in eachslot of the rolling buffer and the average value thereof does not exceeda predefined threshold.
 12. The telematics system of claim 9 whereindetermining whether the first reference data in the rolling buffer meetsa third criterion comprises determining whether a value represented bythe first reference data in each slot of the rolling buffer is within apredefined value of the average value represented thereby.
 13. Thetelematics system of claim 9 wherein the plurality of monitoring devicesfurther configured for collecting a plurality of second reference datacorresponding to a third CAN ID having at least a second correlationrelationship with the first reference data and the manufacturer-specificCAN data; storing the second reference data in the rolling buffer;following receipt of the new first reference data, new second referencedata and the new CAN payload data, determining whether the firstreference data present in the rolling buffer meets a fifth criterion andthe second reference data present in the rolling buffer meets a sixthcriterion; in response to determining the first reference data presentin the rolling buffer meeting the fifth criterion and the secondreference data present in the rolling buffer meeting the sixthcriterion, determining whether one or more second subsets of the CANpayload data present in the rolling buffer meets a fourth criterion,each of the one or more second subsets occupying a second byte positionin each slot of the rolling buffer; dependent on the first referencedata meeting a fifth criterion and the second reference data meeting thesixth criterion exceeding a third counting threshold, for each of theone or more second subsets meeting the fourth criterion exceeding afourth counting threshold, forming second position data indicative ofthe second byte position in each slot of the rolling buffer occupiedthereby; and wherein forming first candidate data indicative of thefirst position data and the first CAN ID comprises forming firstcandidate dependent on the first byte position of the first positiondata and the second byte position of the second position data beingsame, and the first CAN ID.
 14. The telematics system of claim 13wherein the fourth criterion, fifth criterion and the sixth criterionare indicative of the second correlation relationship.
 15. Thetelematics system of claim 13 wherein determining whether the firstreference data present in the rolling buffer meets a fifth criterioncomprises determining whether the value represented by first referencedata in each slot of the rolling buffer is within a predefined value ofthe average thereof.
 16. The telematics system of claim 1 wherein thefirst reference data includes first reference data corresponding to asecond CAN ID and second reference data corresponding to a third CAN ID,the first reference data and the second reference data having at least afirst correlation relationship with the manufacturer-specific CAN data.17. The telematics system of claim 16 wherein determining whether thefirst reference data present in the rolling buffer meets a firstcriterion comprises determining whether the first reference data and thesecond reference data in the rolling buffer meets a first criterion. 18.The telematics system of claim 1 wherein collecting first reference datahaving at least a first correlation relationship with themanufacturer-specific CAN data comprises collecting first reference dataand second reference data having a first correlation relationship withthe manufacturer-specific CAN data.
 19. The telematics system of claim 1wherein selecting from the second candidate data a second candidatecomprises selecting a second candidate indicated in the greatest numberof instances of the second candidate data.